From: Tom Tromey <tromey@redhat.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: "Maciej W. Rozycki" <macro@codesourcery.com>,
justin.lebar@gmail.com, stanshebs@earthlink.net,
gdb-patches@sourceware.org
Subject: Re: Status of 'blacklist' patch?
Date: Thu, 03 Nov 2011 14:32:00 -0000 [thread overview]
Message-ID: <m3k47htgy2.fsf@fleche.redhat.com> (raw)
In-Reply-To: <83fwi5n9nn.fsf@gnu.org> (Eli Zaretskii's message of "Thu, 03 Nov 2011 05:54:04 +0200")
>>>>> "Eli" == Eli Zaretskii <eliz@gnu.org> writes:
Eli> No, please don't remove the @node line. Instead, add to the parent
Eli> node a @menu that mentions this node, or add the node to an existing
Eli> menu, if the parent node already has a menu.
Here is what I am committing to fix the problem.
Tested by building with makeinfo 4.13.
Tom
2011-11-03 Tom Tromey <tromey@redhat.com>
* gdb.texinfo (Stopping): Add menu entry.
(Continuing and Stepping): Restore @node. Use @section, not
@subsection.
Index: gdb.texinfo
===================================================================
RCS file: /cvs/src/src/gdb/doc/gdb.texinfo,v
retrieving revision 1.887
diff -u -r1.887 gdb.texinfo
--- gdb.texinfo 3 Nov 2011 00:16:45 -0000 1.887
+++ gdb.texinfo 3 Nov 2011 14:31:48 -0000
@@ -3216,6 +3216,8 @@
@menu
* Breakpoints:: Breakpoints, watchpoints, and catchpoints
* Continuing and Stepping:: Resuming execution
+* Skipping Over Functions and Files::
+ Skipping over functions and files
* Signals:: Signals
* Thread Stops:: Stopping and starting multi-thread programs
@end menu
@@ -4854,7 +4856,8 @@
An argument is a repeat count, as in @code{next}.
@end table
-@subsection Skipping Over Functions and Files
+@node Skipping Over Functions and Files
+@section Skipping Over Functions and Files
@cindex skipping over functions and files
The program you are debugging may contain some functions which are
next prev parent reply other threads:[~2011-11-03 14:32 UTC|newest]
Thread overview: 44+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-06 12:12 Diego Novillo
2011-10-06 14:08 ` Justin Lebar
2011-10-06 15:51 ` Stan Shebs
2011-10-06 20:16 ` Justin Lebar
2011-10-10 12:34 ` Stan Shebs
2011-10-11 21:34 ` Justin Lebar
2011-10-11 23:54 ` Doug Evans
2011-10-16 19:22 ` Justin Lebar
2011-10-20 19:46 ` Tom Tromey
2011-10-25 20:07 ` Justin Lebar
2011-10-25 20:41 ` Pedro Alves
2011-10-25 21:25 ` Justin Lebar
2011-10-20 20:40 ` Eli Zaretskii
2011-10-25 16:47 ` Justin Lebar
2011-10-25 16:53 ` Eli Zaretskii
2011-10-25 19:52 ` Justin Lebar
2011-10-25 20:13 ` Eli Zaretskii
2011-10-25 20:30 ` Justin Lebar
2011-10-26 1:06 ` Stan Shebs
2011-10-26 3:45 ` Justin Lebar
2011-10-26 5:37 ` Stan Shebs
2011-10-26 8:10 ` Joel Brobecker
2011-10-26 13:28 ` Eli Zaretskii
2011-10-26 15:11 ` Justin Lebar
2011-10-28 18:18 ` Tom Tromey
2011-10-28 19:48 ` Justin Lebar
2011-10-28 19:53 ` Tom Tromey
2011-10-28 19:49 ` Tom Tromey
2011-10-28 19:55 ` Justin Lebar
2011-10-28 20:37 ` Tom Tromey
2011-10-31 15:52 ` Justin Lebar
[not found] ` <4EAF2E0E.7080508@earthlink.net>
2011-11-01 14:53 ` Justin Lebar
2011-11-02 22:43 ` Maciej W. Rozycki
2011-11-02 23:52 ` Stan Shebs
2011-11-03 0:20 ` Maciej W. Rozycki
2011-11-03 3:54 ` Eli Zaretskii
2011-11-03 14:32 ` Tom Tromey [this message]
2011-11-03 16:54 ` Eli Zaretskii
2011-11-03 18:04 ` Maciej W. Rozycki
2011-11-03 18:25 ` Eli Zaretskii
2011-11-03 19:01 ` Stan Shebs
2011-10-06 17:19 ` Diego Novillo
2011-10-06 17:33 ` Tom Tromey
2011-10-06 17:37 ` Diego Novillo
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=m3k47htgy2.fsf@fleche.redhat.com \
--to=tromey@redhat.com \
--cc=eliz@gnu.org \
--cc=gdb-patches@sourceware.org \
--cc=justin.lebar@gmail.com \
--cc=macro@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