From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 15104 invoked by alias); 30 Jan 2008 13:15:09 -0000 Received: (qmail 15092 invoked by uid 22791); 30 Jan 2008 13:15:08 -0000 X-Spam-Check-By: sourceware.org Received: from NaN.false.org (HELO nan.false.org) (208.75.86.248) by sourceware.org (qpsmtpd/0.31) with ESMTP; Wed, 30 Jan 2008 13:14:48 +0000 Received: from nan.false.org (localhost [127.0.0.1]) by nan.false.org (Postfix) with ESMTP id 6061698234; Wed, 30 Jan 2008 13:14:47 +0000 (GMT) Received: from caradoc.them.org (22.svnf5.xdsl.nauticom.net [209.195.183.55]) by nan.false.org (Postfix) with ESMTP id 12A2798005; Wed, 30 Jan 2008 13:14:46 +0000 (GMT) Received: from drow by caradoc.them.org with local (Exim 4.68) (envelope-from ) id 1JKCm6-0003fB-4s; Wed, 30 Jan 2008 08:14:46 -0500 Date: Wed, 30 Jan 2008 13:18:00 -0000 From: Daniel Jacobowitz To: Eli Zaretskii Cc: pedro_alves@portugalmail.pt, gdb-patches@sourceware.org Subject: Re: [rfc] Multiple process support in gdbserver Message-ID: <20080130131446.GB13702@caradoc.them.org> Mail-Followup-To: Eli Zaretskii , pedro_alves@portugalmail.pt, gdb-patches@sourceware.org References: <20071207212352.GB32256@caradoc.them.org> <20071208152935.GA4888@caradoc.them.org> <20071210153146.GA21899@caradoc.them.org> <4797EEC9.10100@portugalmail.pt> <20080130005147.GA25780@caradoc.them.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.17 (2007-12-11) X-IsSubscribed: yes Mailing-List: contact gdb-patches-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-patches-owner@sourceware.org X-SW-Source: 2008-01/txt/msg00787.txt.bz2 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 > > 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 * 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.