From: Michael Eager <eager@eagercon.com>
To: Jim Blandy <jimb@codesourcery.com>
Cc: Stan Shebs <stanshebs@earthlink.net>, gdb@sources.redhat.com
Subject: Re: What's an annex? stratum?
Date: Mon, 25 Jun 2007 18:39:00 -0000 [thread overview]
Message-ID: <468009EA.4040504@eagercon.com> (raw)
In-Reply-To: <m3tzsvsyh0.fsf@codesourcery.com>
Jim Blandy wrote:
> For what it's worth --- we don't invest enough time in
> doc/gdbint.texinfo to keep it a clear, accurate reference to the
> code. (For me, at least, this is a deliberate decision.) It's more a
> collection of the clearer explanations that have appeared on the
> mailing list over time.
Unfortunately, much of it is obsolete. Some sections, like 9.6,
make this explicit. Other sections say that the area is in flux,
like section 9.7. Other sections don't tell you that they are
out of date (like the section about libgdb?).
Some important parts are simply missing, like the sections titled
Console Printing, TUI, Frame Interpretation, Inferior Call Setup, and
others.
I don't mean to harp on the documentation, but often the "clearer
explanations" amount to commentary about how the old technique didn't
work well and the new technique is better. That may be true, but it
doesn't reveal much about how to use the technique.
If I get to the point where I think I really understand an area,
I'll be happy to contribute to documentation improvements. I'm
not there at the moment.
--
Michael Eager eager@eagercon.com
1960 Park Blvd., Palo Alto, CA 94306 650-325-8077
next prev parent reply other threads:[~2007-06-25 18:39 UTC|newest]
Thread overview: 41+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-23 18:01 Michael Eager
2007-06-23 18:57 ` Stan Shebs
2007-06-23 19:08 ` Michael Eager
2007-06-23 19:47 ` Eli Zaretskii
2007-06-23 20:51 ` Michael Eager
2007-06-23 21:23 ` Daniel Jacobowitz
2007-06-23 21:40 ` Michael Eager
2007-06-24 2:58 ` Eli Zaretskii
2007-06-24 4:32 ` Michael Eager
2007-06-25 18:03 ` Jim Blandy
2007-06-25 18:39 ` Michael Eager [this message]
2007-06-25 19:10 ` Jim Blandy
2007-06-25 19:26 ` Paul Koning
2007-06-25 19:32 ` Daniel Jacobowitz
2007-06-25 19:38 ` Robert Dewar
2007-06-25 19:48 ` Paul Koning
2007-06-25 20:09 ` Michael Eager
2007-06-25 20:40 ` Robert Dewar
2007-06-25 20:47 ` Robert Dewar
2007-06-25 20:31 ` Eli Zaretskii
2007-06-25 20:44 ` Robert Dewar
2007-06-25 21:00 ` Eli Zaretskii
2007-06-25 21:03 ` Robert Dewar
2007-06-25 21:06 ` Robert Dewar
2007-06-26 18:34 ` Markus Deuling
2007-06-26 18:36 ` Robert Dewar
2007-06-26 21:55 ` Jim Blandy
2007-06-26 22:14 ` Nick Roberts
2007-06-26 23:26 ` Robert Dewar
2007-06-26 23:39 ` Joel Brobecker
2007-06-26 23:43 ` Robert Dewar
2007-06-27 0:32 ` Jim Blandy
2007-06-27 0:42 ` Robert Dewar
2007-06-27 3:22 ` Eli Zaretskii
2007-06-27 0:23 ` Michael Eager
2007-06-25 20:42 ` Eli Zaretskii
2007-06-25 20:23 ` Eli Zaretskii
2007-06-25 21:52 ` Jim Blandy
2007-06-26 1:04 ` Paul Koning
2007-06-25 20:37 ` Eli Zaretskii
2007-06-25 20:15 ` Eli Zaretskii
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=468009EA.4040504@eagercon.com \
--to=eager@eagercon.com \
--cc=gdb@sources.redhat.com \
--cc=jimb@codesourcery.com \
--cc=stanshebs@earthlink.net \
/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