darkkirb/old-cross-binutils
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity

* gdb.texinfo (Startup): Fix last change. Treat gdb.ini like we

Browse source 
do with other non-standard names of init files.
This commit is contained in:
Eli Zaretskii 2005-05-12 09:05:45 +00:00
parent 52d1fb02ab
commit 119b882a3d
2 changed files with 19 additions and 11 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 @@
2005-05-12 Eli Zaretskii <eliz@gnu.org>
* gdb.texinfo (Startup): Fix last change. Treat gdb.ini like we
do with other non-standard names of init files.
2005-05-11 Eli Zaretskii <eliz@gnu.org> 2005-05-11 Eli Zaretskii <eliz@gnu.org>
* gdb.texinfo (Command Files): Move the description of the startup * gdb.texinfo (Command Files): Move the description of the startup

25
gdb/doc/gdb.texinfo
View file

@ -1166,11 +1166,10 @@ Processes command line options and operands.
@item @item
Reads and executes the commands from init file (if any) in the current Reads and executes the commands from init file (if any) in the current
working directory. This is only done if (1) there's an init file in working directory. This is only done if the current directory is
your home directory, and (2) if the current directory is different different from your home directory. Thus, you can have more than one
from your home directory. Thus, you can have more than one init file, init file, one generic in your home directory, and another, specific
one generic in your home directory, and another, specific to the to the program you are debugging, in the directory where you invoke
program you are debugging, in the directory where you invoke
@value{GDBN}. @value{GDBN}.
@item @item
@ -1192,19 +1191,23 @@ option (@pxref{Mode Options, ,Choosing modes}).
@cindex init file name @cindex init file name
@cindex @file{.gdbinit} @cindex @file{.gdbinit}
@cindex @file{gdb.ini} The @value{GDBN} init files are normally called @file{.gdbinit}.
The @value{GDBN} init files are normally called @file{.gdbinit}@footnote{
The DJGPP port of @value{GDBN} uses the name
@file{gdb.ini} instead, due to the limitations of file names imposed
by DOS filesystems.}.
On some configurations of @value{GDBN}, the init file is known by a On some configurations of @value{GDBN}, the init file is known by a
different name (these are typically environments where a specialized different name (these are typically environments where a specialized
form of @value{GDBN} may need to coexist with other forms, hence a form of @value{GDBN} may need to coexist with other forms, hence a
different name for the specialized version's init file). These are the different name for the specialized version's init file). These are the
environments with special init file names: environments with special init file names:
@cindex @file{.vxgdbinit}
@itemize @bullet @itemize @bullet
@cindex @file{gdb.ini}
@item
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.
@cindex @file{.vxgdbinit}
@item @item
VxWorks (Wind River Systems real-time OS): @file{.vxgdbinit} VxWorks (Wind River Systems real-time OS): @file{.vxgdbinit}