This is the mail archive of the
gdb-patches@sourceware.org
mailing list for the GDB project.
Re: [rfc] Infrastructure to disable breakpoints during inferior startup
- From: Tom Tromey <tromey at redhat dot com>
- To: "Ulrich Weigand" <uweigand at de dot ibm dot com>
- Cc: eliz at gnu dot org, thiago dot bauermann at gmail dot com (Thiago Jung Bauermann), gdb-patches at sourceware dot org, pedro at codesourcery dot com, jkratoch at redhat dot com
- Date: Thu, 06 Aug 2009 09:58:54 -0600
- Subject: Re: [rfc] Infrastructure to disable breakpoints during inferior startup
- References: <200908051814.n75IED4s005139@d12av02.megacenter.de.ibm.com>
- Reply-to: Tom Tromey <tromey at redhat dot com>
Ulrich> I'll be happy to add documentation to gdbint.texinfo, but I'm
Ulrich> not quite sure where to start.
It seems to me that in many cases the documentation would be more
helpful if it were near the things it documented.
For example, consider all the text in gdbint.texinfo concerning
cleanups. It is quite useful to read when one is new to GDB; I've
pointed several people at it. However, I think that if it were comments
near the declarations of cleanup functions in a header file, I probably
would not have to point people to it -- they would read it naturally as
a consequence of looking up calls to make_cleanup.
Also, it is simpler to remember to require changes to comments near the
code than to gdbint.texinfo.
I think there is still a need for an internals document, because there
are things worth documenting that don't have a natural location in a
source file. I'm thinking of things like coding conventions, HIG
guidelines for new commands, etc -- things that affect future decisions
but that are not inherent in the code.
Tom