* gdb.texinfo (Separate Debug Files): Use plural form for global
	debugging information directory.
This commit is contained in:
Jan Kratochvil
2012-05-12 14:20:31 +00:00
parent 9920b1ee65
commit f307c045ad
2 changed files with 14 additions and 8 deletions

View File

@ -1,3 +1,9 @@
2012-05-12 Jan Kratochvil <jan.kratochvil@redhat.com>
Eli Zaretskii <eliz@gnu.org>
* gdb.texinfo (Separate Debug Files): Use plural form for global
debugging information directory.
2012-05-11 Stan Shebs <stan@codesourcery.com> 2012-05-11 Stan Shebs <stan@codesourcery.com>
Kwok Cheung Yeung <kcy@codesourcery.com> Kwok Cheung Yeung <kcy@codesourcery.com>

View File

@ -16287,7 +16287,7 @@ Show whether a source file may have multiple base names.
@cindex debugging information in separate files @cindex debugging information in separate files
@cindex @file{.debug} subdirectories @cindex @file{.debug} subdirectories
@cindex debugging information directory, global @cindex debugging information directory, global
@cindex global debugging information directory @cindex global debugging information directories
@cindex build ID, and separate debugging files @cindex build ID, and separate debugging files
@cindex @file{.build-id} directory @cindex @file{.build-id} directory
@ -16332,14 +16332,14 @@ uses two different methods of looking for the debug file:
@item @item
For the ``debug link'' method, @value{GDBN} looks up the named file in For the ``debug link'' method, @value{GDBN} looks up the named file in
the directory of the executable file, then in a subdirectory of that the directory of the executable file, then in a subdirectory of that
directory named @file{.debug}, and finally under the global debug directory named @file{.debug}, and finally under each one of the global debug
directory, in a subdirectory whose name is identical to the leading directories, in a subdirectory whose name is identical to the leading
directories of the executable's absolute file name. directories of the executable's absolute file name.
@item @item
For the ``build ID'' method, @value{GDBN} looks in the For the ``build ID'' method, @value{GDBN} looks in the
@file{.build-id} subdirectory of the global debug directory for a file @file{.build-id} subdirectory of each one of the global debug directories for
named @file{@var{nn}/@var{nnnnnnnn}.debug}, where @var{nn} are the a file named @file{@var{nn}/@var{nnnnnnnn}.debug}, where @var{nn} are the
first 2 hex characters of the build ID bit string, and @var{nnnnnnnn} first 2 hex characters of the build ID bit string, and @var{nnnnnnnn}
are the rest of the bit string. (Real build ID strings are 32 or more are the rest of the bit string. (Real build ID strings are 32 or more
hex characters, not 10.) hex characters, not 10.)
@ -16348,7 +16348,7 @@ hex characters, not 10.)
So, for example, suppose you ask @value{GDBN} to debug So, for example, suppose you ask @value{GDBN} to debug
@file{/usr/bin/ls}, which has a debug link that specifies the @file{/usr/bin/ls}, which has a debug link that specifies the
file @file{ls.debug}, and a build ID whose value in hex is file @file{ls.debug}, and a build ID whose value in hex is
@code{abcdef1234}. If the global debug directory is @code{abcdef1234}. If the list of the global debug directories includes
@file{/usr/lib/debug}, then @value{GDBN} will look for the following @file{/usr/lib/debug}, then @value{GDBN} will look for the following
debug information files, in the indicated order: debug information files, in the indicated order:
@ -16363,8 +16363,8 @@ debug information files, in the indicated order:
@file{/usr/lib/debug/usr/bin/ls.debug}. @file{/usr/lib/debug/usr/bin/ls.debug}.
@end itemize @end itemize
You can set the global debugging info directory's name, and view the You can set the global debugging info directories, and view the
name @value{GDBN} is currently using. list @value{GDBN} is currently using.
@table @code @table @code