Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: "Breazeal, Don" <donb@codesourcery.com>
Cc: Don_Breazeal@mentor.com, gdb-patches@sourceware.org
Subject: Re: [PATCH v7 7/7] Extended-remote follow fork documentation
Date: Fri, 10 Apr 2015 18:29:00 -0000	[thread overview]
Message-ID: <83r3rrsupf.fsf@gnu.org> (raw)
In-Reply-To: <55281342.1050901@codesourcery.com>

> 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.


  reply	other threads:[~2015-04-10 18:29 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 1/7] Identify remote fork event support Don Breazeal
2015-04-15 15:37   ` Pedro Alves
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 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 [this message]
2015-04-10 20:43         ` Don Breazeal
2015-04-15 15:47           ` Pedro Alves
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=83r3rrsupf.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=Don_Breazeal@mentor.com \
    --cc=donb@codesourcery.com \
    --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