This is the mail archive of the gdb-patches@sourceware.org mailing list for the GDB project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

[doc patch] Fix '.debug_gdb_scripts section' node name for info


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


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]