Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Hui Zhu <hui_zhu@mentor.com>
Cc: gdb-patches@sourceware.org, stan_shebs@mentor.com
Subject: Re: [PATCH] Add autoload-breakpoints [3/7] ReportAsync-doc
Date: Sat, 17 Mar 2012 10:12:00 -0000	[thread overview]
Message-ID: <83y5qz359r.fsf@gnu.org> (raw)
In-Reply-To: <4F6450D2.9030109@mentor.com>

> Date: Sat, 17 Mar 2012 16:52:34 +0800
> From: Hui Zhu <hui_zhu@mentor.com>
> CC: Stan Shebs <stan_shebs@mentor.com>
> 
> This is patch for the doc about ReportAsync.

Thanks.

> +The @value{GDBN} remote serial protocol includes @dfn{reportasync},
> +packets that the stub can report status or do an operation in any time.

I don't understand the "do an operation in any time" part.  What does
it mean in practice?

> +When the stub want send @dfn{reportasync} packets, it send shake hands
> +packet @samp{^} to @value{GDBN}.

 When the stub wants to send a @samp{reportasync} packet, it first sends
 a handshake packet @samp{^} to @value{GDBN}.

> +If @value{GDBN} reply a @samp{^}, the shake hands is successful.

 If @value{GDBN} replies with a @samp{^}, the handshake is successful.

> +If not, the shake hands is fail and this packet need to be handle
> +as a simple packet.

 If not, the handshake fails, and the @samp{reportasync} packet needs
 to be handled as a simple packet.

And I don't understand what you mean by "needs to be handled as a
simple packet".  If that's a reference to something discussed earlier
in the manual, please add here a cross-reference to that part.

> +After shake hands, the stub can send packet to @value{GDBN}, the packet
> +format is same with simple remote serial protocol.

 After the handshake, the stub can send @samp{reportasync} packets to
 @value{GDBN}, using the same packet format as in simple remote serial
 protocol.

Is this only for the failed handshake?  If so, perhaps we need to tell
what happens when the handshake succeeds.


  reply	other threads:[~2012-03-17 10:12 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-03-17  8:52 Hui Zhu
2012-03-17 10:12 ` Eli Zaretskii [this message]
2012-03-20 13:25   ` Hui Zhu
2012-03-20 17:30     ` Eli Zaretskii
2012-03-21  7:23       ` Hui Zhu
2012-03-21 18:28         ` Eli Zaretskii
2012-03-22  2:48           ` Hui Zhu
2012-03-26  2:21             ` Hui Zhu
2012-03-31  6:04               ` Eli Zaretskii
2012-04-02  9:10                 ` Hui Zhu

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=83y5qz359r.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=gdb-patches@sourceware.org \
    --cc=hui_zhu@mentor.com \
    --cc=stan_shebs@mentor.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