diff options
| author | Jan Kratochvil <jan.kratochvil@redhat.com> | 2012-08-07 16:49:38 +0000 |
|---|---|---|
| committer | Jan Kratochvil <jan.kratochvil@redhat.com> | 2012-08-07 16:49:38 +0000 |
| commit | dc1039df6354fe0931769191e1413a624ad5697d (patch) | |
| tree | 49c3ca9ccac81ab87d65c1c938a2cfdb27e81b2f /gdb/doc | |
| parent | a988325c2410b0ce11675fd262940bdc030f6bff (diff) | |
| download | gdb-dc1039df6354fe0931769191e1413a624ad5697d.zip gdb-dc1039df6354fe0931769191e1413a624ad5697d.tar.gz gdb-dc1039df6354fe0931769191e1413a624ad5697d.tar.bz2 | |
gdb/doc/
* gdbint.texinfo (Debugging GDB): In section
'Debugging @value{GDBN} with itself' change .gdbinit for gdb-gdb.gdb.
Mention also gdb-gdb.py.
Diffstat (limited to 'gdb/doc')
| -rw-r--r-- | gdb/doc/ChangeLog | 6 | ||||
| -rw-r--r-- | gdb/doc/gdbint.texinfo | 10 |
2 files changed, 11 insertions, 5 deletions
diff --git a/gdb/doc/ChangeLog b/gdb/doc/ChangeLog index 4ef177f..b8cd695 100644 --- a/gdb/doc/ChangeLog +++ b/gdb/doc/ChangeLog @@ -1,3 +1,9 @@ +2012-08-07 Jan Kratochvil <jan.kratochvil@redhat.com> + + * gdbint.texinfo (Debugging GDB): In section + 'Debugging @value{GDBN} with itself' change .gdbinit for gdb-gdb.gdb. + Mention also gdb-gdb.py. + 2012-08-07 Yao Qi <yao@codesourcery.com> Revert the folloing patch: diff --git a/gdb/doc/gdbint.texinfo b/gdb/doc/gdbint.texinfo index 5e00f1f..c4c1cc9 100644 --- a/gdb/doc/gdbint.texinfo +++ b/gdb/doc/gdbint.texinfo @@ -8030,11 +8030,11 @@ debugged in another. Rather than typing the command @kbd{@w{./gdb ./gdb}}, which works on Suns and such, you can copy @file{gdb} to @file{gdb2} and then type @kbd{@w{./gdb ./gdb2}}. -When you run @value{GDBN} in the @value{GDBN} source directory, it will read a -@file{.gdbinit} file that sets up some simple things to make debugging -gdb easier. The @code{info} command, when executed without a subcommand -in a @value{GDBN} being debugged by gdb, will pop you back up to the top level -gdb. See @file{.gdbinit} for details. +When you run @value{GDBN} in the @value{GDBN} source directory, it will read +@file{gdb-gdb.gdb} file (plus possibly @file{gdb-gdb.py} file) that sets up +some simple things to make debugging gdb easier. The @code{info} command, when +executed without a subcommand in a @value{GDBN} being debugged by gdb, will pop +you back up to the top level gdb. See @file{gdb-gdb.gdb} for details. If you use emacs, you will probably want to do a @code{make TAGS} after you configure your distribution; this will put the machine dependent |