Re: [rfc] Multiple process support in gdbserver

[Daniel Jacobowitz <drow@false.org>]

On Wed, Jan 30, 2008 at 06:20:26AM +0200, Eli Zaretskii wrote:
> > Date: Tue, 29 Jan 2008 19:51:47 -0500
> > From: Daniel Jacobowitz <drow@false.org>
> > Cc: gdb-patches@sourceware.org
> > 
> > +Then you can connect using @code{target extended-remote} and start
> > +the program you want to debug.
> 
> The command you suggest to use (target extended-remote) is something
> the user should type on her keyboard, so it should be in @kbd, not
> @code.  (In general, @code is wrong for more than one word at a time.)

Thanks for the explanation; hopefully I can remember that.  I checked
this in to fix it.

-- 
Daniel Jacobowitz
CodeSourcery

2008-01-30  Daniel Jacobowitz  <dan@codesourcery.com>

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

Index: gdb.texinfo
===================================================================
RCS file: /cvs/src/src/gdb/doc/gdb.texinfo,v
retrieving revision 1.464
diff -u -p -r1.464 gdb.texinfo
--- gdb.texinfo	30 Jan 2008 13:11:15 -0000	1.464
+++ gdb.texinfo	30 Jan 2008 13:12:59 -0000
@@ -13044,7 +13044,7 @@ When you connect to @code{gdbserver} usi
 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.