Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Pedro Alves <palves@redhat.com>
To: Don Breazeal <donb@codesourcery.com>,
	gdb-patches@sourceware.org,        eliz@gnu.org
Subject: Re: [PATCH v7 7/7] Extended-remote follow fork documentation
Date: Wed, 15 Apr 2015 15:47:00 -0000	[thread overview]
Message-ID: <552E87F1.3060806@redhat.com> (raw)
In-Reply-To: <1428698594-22772-1-git-send-email-donb@codesourcery.com>

On 04/10/2015 09:43 PM, Don Breazeal wrote:

>  @tab @code{hbreak}
>  
> +@item @code{fork-event-feature}
> +@tab @code{fork stop reason}
> +@tab @code{fork}
> +
> +@item @code{vfork-event-feature}
> +@tab @code{vfork stop reason}
> +@tab @code{vfork}
> +
>  @end multitable
>  
>  @node Remote Stub
> @@ -35286,6 +35297,45 @@ The @var{r} part must be left empty.
>  
>  The same remarks about @samp{qSupported} and non-stop mode above
>  apply.
> +
> +@cindex fork events, remote reply
> +@item fork
> +The packet indicates that @code{fork} was called, and @var{r}
> +is the ptid of the new child process.  This packet is only

I don't think we document what a ptid is --- that's an internal
gdb implementation detail.  This should probably say that it's the
thread id of the new child process, and cross reference
to "thread-id syntax".

> +applicable to targets that support fork events.

Thanks,
Pedro Alves


  reply	other threads:[~2015-04-15 15:47 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-04-10 17:09 [PATCH v7 0/7] Remote fork events Don Breazeal
2015-04-10 17:10 ` [PATCH v7 3/7] Extended-remote Linux follow fork Don Breazeal
2015-04-15 15:38   ` Pedro Alves
2015-04-10 17:10 ` [PATCH v7 1/7] Identify remote fork event support Don Breazeal
2015-04-15 15:37   ` Pedro Alves
2015-04-10 17:10 ` [PATCH v7 2/7] Clone remote breakpoints Don Breazeal
2015-04-10 17:10 ` [PATCH v7 4/7] Arch-specific remote follow fork Don Breazeal
2015-04-10 17:11 ` [PATCH v7 7/7] Extended-remote follow fork documentation Don Breazeal
2015-04-10 17:56   ` Eli Zaretskii
2015-04-10 18:15     ` Breazeal, Don
2015-04-10 18:29       ` Eli Zaretskii
2015-04-10 20:43         ` Don Breazeal
2015-04-15 15:47           ` Pedro Alves [this message]
2015-04-10 17:11 ` [PATCH v7 6/7] Remote fork catch Don Breazeal
2015-04-15 15:39   ` Pedro Alves
2015-04-10 17:11 ` [PATCH v7 5/7] Remote follow vfork Don Breazeal
2015-04-15 15:38   ` Pedro Alves
2015-04-15 15:41     ` 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=552E87F1.3060806@redhat.com \
    --to=palves@redhat.com \
    --cc=donb@codesourcery.com \
    --cc=eliz@gnu.org \
    --cc=gdb-patches@sourceware.org \
    /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