From: Daniel Jacobowitz <drow@false.org>
To: Nick Roberts <nickrob@snap.net.nz>
Cc: gdb-patches@sources.redhat.com
Subject: Re: [PATCH] Doc: detach-on-follow
Date: Tue, 29 Jan 2008 16:50:00 -0000 [thread overview]
Message-ID: <20080129164858.GA1637@caradoc.them.org> (raw)
In-Reply-To: <18251.27455.529796.608240@kahikatea.snap.net.nz>
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
next prev parent reply other threads:[~2008-01-29 16:49 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-27 0:57 Nick Roberts
2008-01-29 16:50 ` Daniel Jacobowitz [this message]
2008-01-29 21:17 ` Eli Zaretskii
2008-01-29 21:45 ` Daniel Jacobowitz
2008-01-29 23:34 ` Nick Roberts
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20080129164858.GA1637@caradoc.them.org \
--to=drow@false.org \
--cc=gdb-patches@sources.redhat.com \
--cc=nickrob@snap.net.nz \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox