OpenE2K
/
binutils-gdb
12
0
Fork 0
Code Issues Pull Requests Releases Wiki Activity

document gdb.init check only performed in home directory 

The documentation is a little ambiguous and might be suggesting that
GDB checks all locations where a gdbinit might be located for gdb.ini
files.  This clarifies the current situation.

gdb/doc/ChangeLog:

        * gdb.texinfo (Startup): Minor rewording, and clarify scope of
        gdb.ini warning for Windows port.
This commit is contained in:
Joel Brobecker 2012-11-08 22:26:31 +00:00
parent 9015683b1c
commit 4d3f93a25a
2 changed files with 8 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

5
gdb/doc/ChangeLog
View File

@ -1,3 +1,8 @@
2012-11-08 Joel Brobecker <brobecker@adacore.com>
* gdb.texinfo (Startup): Minor rewording, and clarify scope of
gdb.ini warning for Windows port.
2012-11-08 Yao Qi <yao@codesourcery.com>
* gdb.texinfo (Search): Add kindex for 'fo'.

6
gdb/doc/gdb.texinfo
View File

@ -1366,9 +1366,9 @@ can use @kbd{gdb --help}.
The @value{GDBN} init files are normally called @file{.gdbinit}.
The DJGPP port of @value{GDBN} uses the name @file{gdb.ini}, due to
the limitations of file names imposed by DOS filesystems. The Windows
ports of @value{GDBN} use the standard name, but if they find a
@file{gdb.ini} file, they warn you about that and suggest to rename
the file to the standard name.
port of @value{GDBN} uses the standard name, but if it finds a
@file{gdb.ini} file in your home directory, it warns you about that
and suggests to rename the file to the standard name.
@node Quitting GDB