From: Duane Ellis <duane_ellis@franklin.com>
To: insight@sourceware.cygnus.com
Subject: Re: RFC: gdbtk/TODO file
Date: Tue, 10 Oct 2000 15:29:00 -0000 [thread overview]
Message-ID: <200010102229.SAA28413@mercury.franklin.com> (raw)
In-Reply-To: <Pine.SOL.3.91.1001009174009.24075L-100000@cse.cygnus.com>
On Thu, 5 Oct 2000, Fernando Nasser wrote:
> TODO:
I live in an embedded world; I would add:
1) Better support for assembly language debugging.
In mixed and assembly mode - in effect, the source window would be
a virtual window with no real top or bottom, and not be bound to
the limits of the C file you are viewing.
For instance, your I/O routines may be functions contained in a ROM
monitor (and not part of your program), and you would like to
assembly single step through them.
Or maybe you have a library with no symbolic information but need
to debug anyway.
2) A way of telling the GUI to reset and reconfigure it self.
Change the program counter to an arbitrary address. Now tell
insight's source window (and all others) to fix them selves.
ie: (gdb) set $pc=0x12345678
How do I get the GUI to update it self to the new PC location?
(Happens with simulators & rom targets when you issue a target
command that GDB passes through and cannot understand)
3) The Ability to run without a target, and no symbols.
[this is in a ROM or simulator world]
Load and attach to the target (simulator or rom monitor) issue
various "target/simulator" commands that make the program load into
memory. (that GDB does not know about, nor can you explain to GDB
in any way)
GDB can't seem to run unless it has loaded a file. That's not
always required.
-Duane.
next prev parent reply other threads:[~2000-10-10 15:29 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-10-05 13:35 Fernando Nasser
2000-10-09 17:48 ` Mo DeJong
2000-10-10 8:02 ` Fernando Nasser
2000-10-10 15:29 ` Duane Ellis [this message]
2000-10-10 18:32 ` Fernando Nasser
2000-10-11 6:28 ` Duane Ellis
2000-10-11 9:47 ` Fernando Nasser
2000-10-11 9:58 ` Keith Seitz
2000-10-11 10:08 ` Fernando Nasser
2000-10-11 10:12 ` Duane Ellis
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=200010102229.SAA28413@mercury.franklin.com \
--to=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).