This is the mail archive of the
gdb-patches@sourceware.org
mailing list for the GDB project.
Re: [PATCH v7 7/7] Extended-remote follow fork documentation
- From: Pedro Alves <palves at redhat dot com>
- To: Don Breazeal <donb at codesourcery dot com>, gdb-patches at sourceware dot org, eliz at gnu dot org
- Date: Wed, 15 Apr 2015 16:46:57 +0100
- Subject: Re: [PATCH v7 7/7] Extended-remote follow fork documentation
- Authentication-results: sourceware.org; auth=none
- References: <83r3rrsupf dot fsf at gnu dot org> <1428698594-22772-1-git-send-email-donb at codesourcery dot 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