Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Michael Snyder <msnyder@redhat.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: gdb-patches@sources.redhat.com, gdb@sources.redhat.com
Subject: Re: [RFC] multi-process gdb (forks, checkpoints)
Date: Wed, 30 Nov 2005 03:00:00 -0000	[thread overview]
Message-ID: <438CA9FF.30706@redhat.com> (raw)
In-Reply-To: <uek5083rx.fsf@gnu.org>

Eli Zaretskii wrote:
>>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]

Good idea.  But <n>, as written, is not a PID, it's a
small counting number (analogous to a breakpoint id or
thread id).

I've added the command "process <proc-id" on the branch,
but kept "fork <fork-id>" since its semantics is different
(and still useful).  "info processes" is problematic, since
there is already an "info proc" command.




  reply	other threads:[~2005-11-29 19:20 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
2005-11-30  3:00   ` Michael Snyder [this message]
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=438CA9FF.30706@redhat.com \
    --to=msnyder@redhat.com \
    --cc=eliz@gnu.org \
    --cc=gdb-patches@sources.redhat.com \
    --cc=gdb@sources.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