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: Eli Zaretskii <eliz at gnu dot org>
- To: "Breazeal, Don" <donb at codesourcery dot com>
- Cc: Don_Breazeal at mentor dot com, gdb-patches at sourceware dot org
- Date: Fri, 10 Apr 2015 21:29:32 +0300
- Subject: Re: [PATCH v7 7/7] Extended-remote follow fork documentation
- Authentication-results: sourceware.org; auth=none
- References: <1428685786-18094-1-git-send-email-donb at codesourcery dot com> <1428685786-18094-8-git-send-email-donb at codesourcery dot com> <83wq1jsw8m dot fsf at gnu dot org> <55281342 dot 1050901 at codesourcery dot com>
- Reply-to: Eli Zaretskii <eliz at gnu dot org>
> Date: Fri, 10 Apr 2015 11:15:30 -0700
> From: "Breazeal, Don" <donb@codesourcery.com>
> CC: "gdb-patches@sourceware.org" <gdb-patches@sourceware.org>
>
> >> +@cindex fork events, remote reply
> >> +@item fork
> >> +The packet indicates that @code{fork} was called, and @var{r}
> >
> > What does that @var{r} refer to? The previous text mentions
> > @var{n}:@var{r} pairs, but there's no @var{n} in this description, so
> > it doesn't seem to fit. What am I missing?
>
> Maybe I'm the one who is missing something. I thought that the @var{n}
> was implied by '@item fork', because of this text above:
>
> If @var{n} is a recognized @dfn{stop reason},
Sheesh! 2 pages ago...
> In this case @var{n} is a stop reason. Subsequently '@item fork' is in
> this table:
>
> The currently defined stop reasons are:
>
> @table @samp
>
> I pretty much just copied what had been done for shared library events
> in the same table. Should I do this differently? I see that swbreak
> and hwbreak aren't the same as the other items.
Never mind, let's leave it as it is.
Thanks.