[PATCH] Doc: detach-on-follow

[PATCH] Doc: detach-on-follow

[Nick Roberts]

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  <nickrob@snap.net.nz>

	* 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

Re: [PATCH] Doc: detach-on-follow

[Daniel Jacobowitz]

On Tue, Nov 27, 2007 at 01:56:31PM +1300, Nick Roberts wrote:
> 
> 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  <nickrob@snap.net.nz>
> 
> 	* gdb.texinfo (Processes): Mention process command.
> 	detach-on-follow -> detach-on-fork.

This patch looks right to me; Eli, is it OK?

> *** 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
> 

-- 
Daniel Jacobowitz
CodeSourcery

Re: [PATCH] Doc: detach-on-follow

[Eli Zaretskii]

> Date: Tue, 29 Jan 2008 11:48:58 -0500
> From: Daniel Jacobowitz <drow@false.org>
> Cc: gdb-patches@sources.redhat.com
> 
> > 2007-11-27  Nick Roberts  <nickrob@snap.net.nz>
> > 
> > 	* gdb.texinfo (Processes): Mention process command.
> > 	detach-on-follow -> detach-on-fork.
> 
> This patch looks right to me; Eli, is it OK?

Yes.  (Didn't I review it back then?)

Re: [PATCH] Doc: detach-on-follow

[Daniel Jacobowitz]

On Tue, Jan 29, 2008 at 10:35:45PM +0200, Eli Zaretskii wrote:
> Yes.  (Didn't I review it back then?)

Possibly - I had only the patch saved in my queue.

-- 
Daniel Jacobowitz
CodeSourcery

Re: [PATCH] Doc: detach-on-follow

[Nick Roberts]

 > > > 	* gdb.texinfo (Processes): Mention process command.
 > > > 	detach-on-follow -> detach-on-fork.
 > > 
 > > This patch looks right to me; Eli, is it OK?
 > 
 > Yes.  (Didn't I review it back then?)

If so, I never saw it.  No problem, I've committed it now.

-- 
Nick                                           http://www.inet.net.nz/~nickrob