From: Eli Zaretskii <eliz@gnu.org>
To: Michael Snyder <msnyder@redhat.com>
Cc: gdb-patches@sources.redhat.com, gdb@sources.redhat.com
Subject: Re: [RFC] multi-process gdb (forks, checkpoints)
Date: Tue, 29 Nov 2005 19:20:00 -0000 [thread overview]
Message-ID: <uek5083rx.fsf@gnu.org> (raw)
In-Reply-To: <438B8B6F.6010706@redhat.com> (message from Michael Snyder on Mon, 28 Nov 2005 14:57:51 -0800)
> Date: Mon, 28 Nov 2005 14:57:51 -0800
> From: Michael Snyder <msnyder@redhat.com>
>
> This is, no kidding, gdb debugging multiple processes.
Wow! Thanks!
> Eli, I'll be working on documentation. For the mean time,
> the user interface looks like this:
>
> set/show detach-on-fork (on/off) [default on]
> info forks
> fork <n> [analogous to thread <n>]
> detach-fork <n>
> delete-fork <n> [and kill]
I'd prefer that we use ``process'' instead of ``fork'' here. That is,
info processes
process <n> [assuming n is a PID]
detach-process <n>
delete-process <n>
next prev parent reply other threads:[~2005-11-29 4:41 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-29 4:41 Michael Snyder
2005-11-29 19:20 ` Eli Zaretskii [this message]
2005-11-30 3:00 ` Michael Snyder
2005-11-30 5:41 ` Jim Blandy
2005-11-30 11:39 ` Michael Snyder
2005-11-30 13:10 ` Daniel Jacobowitz
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=uek5083rx.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=gdb-patches@sources.redhat.com \
--cc=gdb@sources.redhat.com \
--cc=msnyder@redhat.com \
/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