From: Michael Eager <eager@eagercon.com>
To: gdb@sources.redhat.com
Subject: GDB Documentation and Request for Help
Date: Fri, 30 Mar 2007 17:20:00 -0000 [thread overview]
Message-ID: <460D46B7.10902@eagercon.com> (raw)
I'm trying to move a proprietary target from an old version
of gdb (5.3) to the latest version. Based on seeing that
there was no clear way to translate the existing target support
to the current gdb architecture (and with a little advice from
the mailing list) I decided to create a new port for the target.
So that's coming along, but I'm having trouble figuring out
frame handling, in particular, when and where the current target
registers are read into the current frame. After stumbling around
tracing the code for a while, I decided to take the plunge and
actually (re-)read the gdb internals document.
So I found the description of frames and the sentinel frame.
Not where I had been looking, under the chapter titled Target
Architecture Definition, but by accident, under Algorithms.
Under the former section, I found what I was looking for:
FRAME_INIT_SAVED_REGISTERS, now renamed DEPRECATED_. But when
I look in the code, I find that this was removed in 2004.
So the gdb internals document comes close to being useless,
IMO. There are several sections which are empty, others which
declare themselves to be obsolete, parts which are more-or-less
unclear, and worse, parts which appear to explain the internals
but are several years out of date.
If someone would volunteer to spend an hour or two helping me
understand frame handling and what parts of the Architecture
Definition section are (as the politicos say) no longer
operative, and what they should say, I'll update the document
to incorporate those changes. I won't rewrite the gdb internals
document, although it really needs this, but even removing
misleading text would be an improvement.
Thanks in advance!
--
Michael Eager eager@eagercon.com
1960 Park Blvd., Palo Alto, CA 94306 650-325-8077
next reply other threads:[~2007-03-30 17:20 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-30 17:20 Michael Eager [this message]
2007-03-30 18:08 ` Jim Blandy
2007-03-30 18:27 ` Michael Eager
2007-03-30 18:41 ` Daniel Jacobowitz
2007-03-30 21:02 ` Jim Blandy
2007-03-30 21:14 ` Michael Eager
2007-03-31 8:29 ` Eli Zaretskii
2007-04-04 14:57 ` Dave Korn
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=460D46B7.10902@eagercon.com \
--to=eager@eagercon.com \
--cc=gdb@sources.redhat.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