From: Jim Blandy <jimb@codesourcery.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: eager@eagercon.com, stanshebs@earthlink.net, gdb@sources.redhat.com
Subject: Re: What's an annex? stratum?
Date: Mon, 25 Jun 2007 21:52:00 -0000 [thread overview]
Message-ID: <m3myyn66t8.fsf@codesourcery.com> (raw)
In-Reply-To: <umyynokba.fsf@gnu.org> (Eli Zaretskii's message of "Mon, 25 Jun 2007 23:23:05 +0300")
Eli Zaretskii <eliz@gnu.org> writes:
>> Cc: Stan Shebs <stanshebs@earthlink.net>, gdb@sources.redhat.com
>> From: Jim Blandy <jimb@codesourcery.com>
>> Date: Mon, 25 Jun 2007 12:10:36 -0700
>>
>> Well, let me try again to say what I meant: if you're new to GDB, you
>> should not start by reading gdbint.texinfo. Instead, start by reading
>> and grepping, and then experiment by debugging GDB with itself.
>
> That may be the only practical way today, but IMO it's a terribly
> inefficient way. GDB's sources is a hodgepodge of many disparate and
> not always related parts: different target-specific back-ends that
> have no relation whatsoever, semi-obsolete APIs used by a couple of
> rotting targets, features relevant only to remote debugging that are
> not clearly separated from the native pieces, etc. For the
> uninitiated, finding one's way in all this maze of twisted little
> passages all alike, without some minimal guidance, is a very hard job,
> to say the least.
This is all true.
>> I'm even a little skeptical about the value of internals documentation
>> at all.
>
> I cannot disagree more. A well written, well indexed internal
> documentation can be a real help in studying an unfamiliar program of
> GDB's complexity.
Well, if GCC's internals documentation is as good as they say, I could
be wrong.
next prev parent reply other threads:[~2007-06-25 21:52 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
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 [this message]
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=m3myyn66t8.fsf@codesourcery.com \
--to=jimb@codesourcery.com \
--cc=eager@eagercon.com \
--cc=eliz@gnu.org \
--cc=gdb@sources.redhat.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