Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Hui Zhu <hui_zhu@mentor.com>
To: <gdb-patches@sourceware.org>
Cc: Stan Shebs <stan_shebs@mentor.com>
Subject: [PATCH] Add autoload-breakpoints [3/7] ReportAsync-doc
Date: Sat, 17 Mar 2012 08:52:00 -0000	[thread overview]
Message-ID: <4F6450D2.9030109@mentor.com> (raw)

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

Hi,

This is patch for the doc about ReportAsync.

Thanks,
Hui

2012-03-17  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: 1693 bytes --]

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

--- a/doc/gdb.texinfo
+++ b/doc/gdb.texinfo
@@ -33568,6 +33568,7 @@ Show the current setting of the target w
 * Host I/O Packets::
 * Interrupts::
 * Notification Packets::
+* ReportAsync Packets::
 * Remote Non-Stop::
 * Packet Acknowledgment::
 * Examples::
@@ -35474,6 +35475,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::
@@ -36571,6 +36576,26 @@ 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 includes @dfn{reportasync},
+packets that the stub can report status or do an operation in any time.
+If the stub supports @dfn{reportasync}, it should report that to
+@value{GDBN} by including @samp{ReportAsync+} in its @samp{qSupported}
+response (@pxref{qSupported}).
+
+When the stub want send @dfn{reportasync} packets, it send shake hands
+packet @samp{^} to @value{GDBN}.
+If @value{GDBN} reply a @samp{^}, the shake hands is successful.
+If not, the shake hands is fail and this packet need to be handle
+as a simple packet.
+
+After shake hands, the stub can send packet to @value{GDBN}, the packet
+format is same with simple remote serial protocol.
+
 @node Remote Non-Stop
 @section Remote Protocol Support for Non-Stop Mode
 

             reply	other threads:[~2012-03-17  8:52 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-03-17  8:52 Hui Zhu [this message]
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

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=4F6450D2.9030109@mentor.com \
    --to=hui_zhu@mentor.com \
    --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