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

* gdb.texinfo (Command Files): Explain order of init file reading.

This commit is contained in:
Jim Kingdon 1993-10-27 16:20:51 +00:00
parent 90d8edfdf3
commit 64a0145050
2 changed files with 10 additions and 5 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
gdb/doc/ChangeLog
View File

@ -1,5 +1,7 @@
Wed Oct 27 00:25:46 1993 Jim Kingdon (kingdon@lioth.cygnus.com)
* gdb.texinfo (Command Files): Explain order of init file reading.
* remote.texi (Bootstrapping): Talk about getting the serial driver
to deal with ^C sent by gdb to stop the remote system.

13
gdb/doc/gdb.texinfo
View File

@ -7507,11 +7507,14 @@ it would from the terminal.
@cindex init file
@cindex @file{@value{GDBINIT}}
When you start @value{GDBN}, it automatically executes commands from its
@dfn{init files}. These are files named @file{@value{GDBINIT}}. @value{GDBN} reads
the init file (if any) in your home directory and then the init file
(if any) in the current working directory. (The init files are not
executed if you use the @samp{-nx} option; @pxref{Mode Options,
,Choosing modes}.)
@dfn{init files}. These are files named @file{@value{GDBINIT}}.
@value{GDBN} reads the init file (if any) in your home directory, then
processes command line options and operands, and then reads the init
file (if any) in the current working directory. This is so the init
file in your home directory can set options (such as @code{set
complaints} which affect the processing of the command line options and
operands. The init files are not executed if you use the @samp{-nx}
option; @pxref{Mode Options, ,Choosing modes}.
@ifset GENERIC
@cindex init file name