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

* gdb.texinfo (Multi-Process Mode for gdbserver): Use @kbd for 

commands.
This commit is contained in:
Daniel Jacobowitz 2008-01-30 13:14:40 +00:00
parent 5ee187d794
commit 6e6c6f5087
2 changed files with 7 additions and 2 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 @@
2008-01-30 Daniel Jacobowitz <dan@codesourcery.com>
* gdb.texinfo (Multi-Process Mode for gdbserver): Use @kbd for
commands.
2008-01-30 Daniel Jacobowitz <dan@codesourcery.com>
* gdb.texinfo (Setting Catchpoints): Mention features

4
gdb/doc/gdb.texinfo
View File

@ -13044,7 +13044,7 @@ When you connect to @code{gdbserver} using @code{target remote},
program exits, or you detach from it, @value{GDBN} closes the connection
and @code{gdbserver} exits.
If you connect using @code{target extended-remote}, @code{gdbserver}
If you connect using @kbd{target extended-remote}, @code{gdbserver}
enters multi-process mode. When the debugged program exits, or you
detach from it, @value{GDBN} stays connected to @code{gdbserver} even
though no program is running. The @code{run} and @code{attach}
@ -13056,7 +13056,7 @@ redirection (@pxref{Arguments}).
To start @code{gdbserver} without supplying an initial command to run
or process ID to attach, use the @option{--multi} command line option.
Then you can connect using @code{target extended-remote} and start
Then you can connect using @kbd{target extended-remote} and start
the program you want to debug.
@code{gdbserver} does not automatically exit in multi-process mode.