From 6e6c6f5087f4ad1c46f099e0edb175d526ebeee6 Mon Sep 17 00:00:00 2001 From: Daniel Jacobowitz Date: Wed, 30 Jan 2008 13:14:40 +0000 Subject: [PATCH] * gdb.texinfo (Multi-Process Mode for gdbserver): Use @kbd for commands. --- gdb/doc/ChangeLog | 5 +++++ gdb/doc/gdb.texinfo | 4 ++-- 2 files changed, 7 insertions(+), 2 deletions(-) diff --git a/gdb/doc/ChangeLog b/gdb/doc/ChangeLog index 6c67a93..5dcb1f1 100644 --- a/gdb/doc/ChangeLog +++ b/gdb/doc/ChangeLog @@ -1,5 +1,10 @@ 2008-01-30 Daniel Jacobowitz + * gdb.texinfo (Multi-Process Mode for gdbserver): Use @kbd for + commands. + +2008-01-30 Daniel Jacobowitz + * gdb.texinfo (Setting Catchpoints): Mention features supported on GNU/Linux. diff --git a/gdb/doc/gdb.texinfo b/gdb/doc/gdb.texinfo index abe8dd3..923d1ce 100644 --- a/gdb/doc/gdb.texinfo +++ b/gdb/doc/gdb.texinfo @@ -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. -- 2.7.4