From: Keith Seitz <kseitz@firetalk.com>
To: duane_ellis@franklin.com
Cc: insight@sourceware.cygnus.com
Subject: Re: How to get insight to display assembly-language?
Date: Tue, 26 Sep 2000 09:55:00 -0000 [thread overview]
Message-ID: <39D0D4ED.D213DD6A@firetalk.com> (raw)
In-Reply-To: <200009261643.MAA28406@mercury.franklin.com>
Duane Ellis wrote:
>
> As it stands now, (and I believe this to be the fundimental problem)
> the source window is primarally a file viewer for fixed sized
> files. Be the file a true "C" source file, or a 'fake-file' of
> assembly language that was 'constructed/printed/disassembled' into the
> source window.
That's about right. When Insight runs, it disassembles from the file --
not the target, which is why you never see any disassembly output when
you are in ROM code. This is one of the shortcomings of the system right
now. It probably wouldn't be too difficult to hack something in to work,
but it would require a lot of testing.
<shameless-plug>
If anybody is willing to try hacking at it, I would be elated to provide
assistance.
</shameless-plug>
Keith
parent reply other threads:[~2000-09-26 9:55 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <200009261643.MAA28406@mercury.franklin.com>]
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=39D0D4ED.D213DD6A@firetalk.com \
--to=kseitz@firetalk.com \
--cc=duane_ellis@franklin.com \
--cc=insight@sourceware.cygnus.com \
/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).