From: Jan Kratochvil <jan.kratochvil@redhat.com>
To: gdb-patches@sourceware.org
Subject: [doc patch] Fix '.debug_gdb_scripts section' node name for info
Date: Tue, 27 Mar 2012 19:19:00 -0000 [thread overview]
Message-ID: <20120327191903.GA23072@host2.jankratochvil.net> (raw)
Hi Eli,
if you try to jump into the link '.debug_gdb_scripts section' or even just
'n'/'p' navigate around that node you will find it does not work (at least not
in info-4.13a-16.fc17.x86_64).
OK this way or should there be some more name vs. node aliases in the
refeerences?
Thanks,
Jan
gdb/doc/
2012-03-27 Jan Kratochvil <jan.kratochvil@redhat.com>
* gdb.texinfo (Auto-loading): Rename node reference
'.debug_gdb_scripts section' to 'dotdebug_gdb_scripts section'.
Twice.
(.debug_gdb_scripts section): Rename the node ...
(dotdebug_gdb_scripts section): ... here.
(Maintenance Commands): Also rename this node reference.
--- ./gdb/doc/gdb.texinfo 22 Mar 2012 08:10:41 -0000 1.936
+++ ./gdb/doc/gdb.texinfo 27 Mar 2012 19:14:52 -0000
@@ -24717,8 +24717,8 @@ command, or because the inferior has loa
@file{@var{objfile}-gdb.py} and @code{.debug_gdb_scripts} section.
@menu
-* objfile-gdb.py file:: The @file{@var{objfile}-gdb.py} file
-* .debug_gdb_scripts section:: The @code{.debug_gdb_scripts} section
+* objfile-gdb.py file:: The @file{@var{objfile}-gdb.py} file
+* dotdebug_gdb_scripts section:: The @code{.debug_gdb_scripts} section
* Which flavor to choose?::
@end menu
@@ -24744,7 +24744,7 @@ Print the list of all scripts that @valu
Also printed is the list of scripts that were mentioned in
the @code{.debug_gdb_scripts} section and were not found
-(@pxref{.debug_gdb_scripts section}).
+(@pxref{dotdebug_gdb_scripts section}).
This is useful because their names are not printed when @value{GDBN}
tries to load them and fails. There may be many of them, and printing
an error message for each one is problematic.
@@ -24795,7 +24795,7 @@ is the object file's real name, as descr
So your @file{-gdb.py} file should be careful to avoid errors if it
is evaluated more than once.
-@node .debug_gdb_scripts section
+@node dotdebug_gdb_scripts section
@subsubsection The @code{.debug_gdb_scripts} section
@cindex @code{.debug_gdb_scripts} section
@@ -33475,7 +33475,7 @@ If @var{regexp} is specified, only print
matching @var{regexp}.
For each script, this command prints its name as specified in the objfile,
and the full path if known.
-@xref{.debug_gdb_scripts section}.
+@xref{dotdebug_gdb_scripts section}.
@kindex maint print statistics
@cindex bcache statistics
next reply other threads:[~2012-03-27 19:19 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-27 19:19 Jan Kratochvil [this message]
2012-03-27 20:11 ` Eli Zaretskii
2012-03-27 20:16 ` [commit] " Jan Kratochvil
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=20120327191903.GA23072@host2.jankratochvil.net \
--to=jan.kratochvil@redhat.com \
--cc=gdb-patches@sourceware.org \
/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