public inbox for insight@sourceware.org
 help / color / mirror / Atom feed
From: Fernando Nasser <fnasser@redhat.com>
To: Steven Johnson <sbjohnson@ozemail.com.au>
Cc: Insight Mailing List <insight@sourceware.cygnus.com>
Subject: Re: Disassembly Window
Date: Wed, 05 Apr 2000 07:45:00 -0000	[thread overview]
Message-ID: <38EB5137.890574D3@redhat.com> (raw)
In-Reply-To: <38EA5ED1.827206D7@ozemail.com.au>

I have exactly the same problem.  I am connecting to a hardware emulator
and the code is already there (I may not even have the source code at
all).

But it should be an option (as opposed to always on).  

Jim, It would be nice if we could add it, don't you think?

Fernando

P.S.: Steven, are you volunteering? ;-)



Steven Johnson wrote:
> 
> Regarding the Code Display Window,
> 
> Is Insight supposed to show disassembly of the current PC in the main
> code window before any code is loaded? Is there a way to enable this?
> This may not make sense to some people, but for an embedded target like
> mine, just because I havent explicitly loaded a program does not mean
> the disassembly is not interesting, in fact its exactly the opposite.
> 
> Regards,
> Steven Johnson

-- 
Fernando Nasser
Red Hat, Inc. - Toronto                 E-Mail:  fnasser@redhat.com
2323 Yonge Street, Suite #300           Tel:  416-482-2661 ext. 311
Toronto, Ontario   M4P 2C9              Fax:  416-482-6299

  reply	other threads:[~2000-04-05  7:45 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-04-05  0:33 Steven Johnson
2000-04-05  7:45 ` Fernando Nasser [this message]
2000-04-05  9:25   ` James Ingham
2000-04-05  9:47     ` Duane Ellis
2000-04-05 10:42       ` James Ingham
2000-04-06 14:18         ` Steven Johnson
2000-04-06 18:10           ` James Ingham

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=38EB5137.890574D3@redhat.com \
    --to=fnasser@redhat.com \
    --cc=insight@sourceware.cygnus.com \
    --cc=sbjohnson@ozemail.com.au \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).