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

[-- Attachment #1: Type: text/plain, Size: 703 bytes --]

On 03/31/12 14:03, Eli Zaretskii wrote:
>> Date: Mon, 26 Mar 2012 10:21:04 +0800
>> From: Hui Zhu<hui_zhu@mentor.com>
>> CC:<gdb-patches@sourceware.org>,<stan_shebs@mentor.com>
>>
>> +When the stub want send @dfn{reportasync} packets, it send shake hands
>> +packet @samp{^} to @value{GDBN}.
>
>   When the stub wants to send @dfn{reportasync} packets, it should
>   first send a handshake packet @samp{^} to @value{GDBN}.
>
> OK with this change.
>
> Thanks.

Thanks for your help.  I post a new version that is updated according to 
your comments.

Best,
Hui

2012-04-02  Hui Zhu  <hui_zhu@mentor.com>

	* gdb.texinfo (qSupported): Add ReportAsync.
	(Remote Serial Protocol): Add ReportAsync Packets.

[-- Attachment #2: report-doc.txt --]
[-- Type: text/plain, Size: 1571 bytes --]

---
 doc/gdb.texinfo |   23 +++++++++++++++++++++++
 1 file changed, 23 insertions(+)

--- a/doc/gdb.texinfo
+++ b/doc/gdb.texinfo
@@ -33669,6 +33669,7 @@ Show the current setting of the target w
 * Host I/O Packets::
 * Interrupts::
 * Notification Packets::
+* ReportAsync Packets::
 * Remote Non-Stop::
 * Packet Acknowledgment::
 * Examples::
@@ -35575,6 +35576,10 @@ to be enabled and disabled while a trace
 The remote stub supports the @samp{tracenz} bytecode for collecting strings.
 See @ref{Bytecode Descriptions} for details about the bytecode.
 
+@item ReportAsync
+The remote stub supports the @samp{ReportAsync} packet
+(@pxref{ReportAsync Packets}).
+
 @end table
 
 @item qSymbol::
@@ -36672,6 +36677,24 @@ for information on how these notificatio
 @value{GDBN}.
 @end table
 
+@node ReportAsync Packets
+@section ReportAsync Packets
+@cindex reportasync packets
+@cindex packets, reportasync
+
+The @value{GDBN} remote serial protocol supports @dfn{reportasync}
+that can be used asynchronously to report status or send commands.
+
+When the stub wants to send @dfn{reportasync} packets, it should
+first send a handshake packet @samp{^} to @value{GDBN}.
+If @value{GDBN} replies with a @samp{^}, the handshake is successful.
+If not, the handshake fails, and the @samp{reportasync} packet needs
+to be handled as usual.
+
+After the handshake, the stub can send @samp{reportasync} packets to
+@value{GDBN}, using the same packet format as in normal remote serial
+protocol.
+
 @node Remote Non-Stop
 @section Remote Protocol Support for Non-Stop Mode
 

      reply	other threads:[~2012-04-02  9:10 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
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 [this message]

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=4F796CE8.3090405@mentor.com \
    --to=hui_zhu@mentor.com \
    --cc=eliz@gnu.org \
    --cc=gdb-patches@sourceware.org \
    --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