From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 22982 invoked by alias); 27 Nov 2007 00:57:02 -0000 Received: (qmail 22967 invoked by uid 22791); 27 Nov 2007 00:57:01 -0000 X-Spam-Check-By: sourceware.org Received: from viper.snap.net.nz (HELO viper.snap.net.nz) (202.37.101.8) by sourceware.org (qpsmtpd/0.31) with ESMTP; Tue, 27 Nov 2007 00:56:52 +0000 Received: from kahikatea.snap.net.nz (183.63.255.123.dynamic.snap.net.nz [123.255.63.183]) by viper.snap.net.nz (Postfix) with ESMTP id 2B82C3D9FB0 for ; Tue, 27 Nov 2007 13:56:44 +1300 (NZDT) Received: by kahikatea.snap.net.nz (Postfix, from userid 1000) id BF8BE8FC6D; Tue, 27 Nov 2007 13:56:32 +1300 (NZDT) From: Nick Roberts MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <18251.27455.529796.608240@kahikatea.snap.net.nz> Date: Tue, 27 Nov 2007 00:57:00 -0000 To: gdb-patches@sources.redhat.com Subject: [PATCH] Doc: detach-on-follow X-Mailer: VM 7.19 under Emacs 23.0.50.3 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: 2007-11/txt/msg00498.txt.bz2 There is no detach-on-follow but I'm not sure what obvious means anymore. Also mention process command. -- Nick http://www.inet.net.nz/~nickrob 2007-11-27 Nick Roberts * gdb.texinfo (Processes): Mention process command. detach-on-follow -> detach-on-fork. *** gdb.texinfo.~1.446.~ 2007-11-18 13:23:21.000000000 +1300 --- gdb.texinfo 2007-11-27 13:50:48.000000000 +1300 *************** is held suspended. *** 2535,2546 **** @end table ! @kindex show detach-on-follow ! @item show detach-on-follow ! Show whether detach-on-follow mode is on/off. @end table ! If you choose to set @var{detach-on-follow} mode off, then @value{GDBN} will retain control of all forked processes (including nested forks). You can list the forked processes under the control of @value{GDBN} by using the @w{@code{info forks}} command, and switch --- 2535,2546 ---- @end table ! @kindex show detach-on-fork ! @item show detach-on-fork ! Show whether detach-on-fork mode is on/off. @end table ! If you choose to set @samp{detach-on-fork} mode off, then @value{GDBN} will retain control of all forked processes (including nested forks). You can list the forked processes under the control of @value{GDBN} by using the @w{@code{info forks}} command, and switch *************** Print a list of all forked processes und *** 2553,2565 **** The listing will include a fork id, a process id, and the current position (program counter) of the process. - @kindex fork @var{fork-id} @item fork @var{fork-id} Make fork number @var{fork-id} the current process. The argument @var{fork-id} is the internal fork number assigned by @value{GDBN}, as shown in the first field of the @samp{info forks} display. @end table To quit debugging one of the forked processes, you can either detach --- 2553,2570 ---- The listing will include a fork id, a process id, and the current position (program counter) of the process. @kindex fork @var{fork-id} @item fork @var{fork-id} Make fork number @var{fork-id} the current process. The argument @var{fork-id} is the internal fork number assigned by @value{GDBN}, as shown in the first field of the @samp{info forks} display. + @kindex process @var{process-id} + @item process @var{process-id} + Make process number @var{process-id} the current process. The + argument @var{process-id} must be one that is listed in the output of + @samp{info forks}. + @end table To quit debugging one of the forked processes, you can either detach