Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Pedro Alves <pedro@codesourcery.com>
Cc: msnyder@vmware.com, gdb-patches@sourceware.org
Subject: Re: Move the multi-forks support to the generic multi-inferiors support.
Date: Wed, 01 Jul 2009 19:16:00 -0000	[thread overview]
Message-ID: <83y6r82p08.fsf@gnu.org> (raw)
In-Reply-To: <200907011927.59624.pedro@codesourcery.com>

> From: Pedro Alves <pedro@codesourcery.com>
> Date: Wed, 1 Jul 2009 19:27:59 +0100
> Cc: "gdb-patches@sourceware.org" <gdb-patches@sourceware.org>,
>  Eli Zaretskii <eliz@gnu.org>
> 
> Eli, what do you think of this (and of the docs changes)?

I'm fine with it, but I have a couple of comments about the docs.

> +from it by using the @w{@code{detach inferior}} command (allowing it
> +to run independently), or kill it using the @w{@code{kill inferior}}
> +command.  Again, @pxref{Inferiors, ,Debugging Multiple Inferiors}.

@pxref is inappropriate here, since it is designed to be used inside
parentheses.  You want "see @ref" instead.

And I would lose the "Again" part (in which case you can simply use
@xref).

> +info inferiors
> +  List the inferiors currently under GDB's control.
> +
> +inferior NUM
> +  Switch focus to inferior number NUM.
> +
> +detach inferior NUM
> +  Detach from inferior number NUM.
> +
> +kill inferior NUM
> +  Kill inferior number NUM.

I think this deserves a short intro, like one or two sentences saying
something about multi-inferior debugging.

> +process PID
> +  Removed.

Perhaps say something about replacement command(s), or why none is
needed.

Thanks.


  reply	other threads:[~2009-07-01 19:16 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-05-30 23:13 Pedro Alves
2009-05-31 20:46 ` Tom Tromey
2009-05-31 22:07   ` Pedro Alves
2009-05-31 22:23     ` Doug Evans
2009-06-01 15:58     ` Tom Tromey
2009-06-06  0:09       ` Tom Tromey
2009-06-06 16:06         ` Pedro Alves
2009-06-08  1:34           ` Marc Khouzam
2009-06-08 22:43             ` Tom Tromey
2009-06-08 23:22               ` Pedro Alves
2009-06-08 22:39           ` Tom Tromey
2009-06-08 23:16             ` Pedro Alves
2009-06-10 22:09               ` Tom Tromey
2009-06-10 22:13                 ` Pedro Alves
2009-06-08 12:58 ` Pedro Alves
2009-06-11 19:32 ` Michael Snyder
2009-07-01 18:27   ` Pedro Alves
2009-07-01 19:16     ` Eli Zaretskii [this message]
2009-07-02 14:32       ` Pedro Alves
2009-07-02 19:00         ` Eli Zaretskii
2009-07-02 21:59           ` Pedro Alves

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=83y6r82p08.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=gdb-patches@sourceware.org \
    --cc=msnyder@vmware.com \
    --cc=pedro@codesourcery.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