Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Vladimir Prus <vladimir@codesourcery.com>
To: gdb-patches@sources.redhat.com
Subject: [RFA] [doc] thread-created/thread-exited
Date: Sat, 26 Apr 2008 17:54:00 -0000	[thread overview]
Message-ID: <200804262144.03702.vladimir@codesourcery.com> (raw)


This patch documents the thread-create and thread-exited MI notification.
It also fixes the terminology as bit -- the grammar say that out-of-band
record is either async record or stream record, whereas the following docs
first describe stream records and then talk about async records, but call
them out-of-band.

OK?

- Volodya

---
 gdb/doc/gdb.texinfo |   23 ++++++++++++++---------
 1 files changed, 14 insertions(+), 9 deletions(-)

diff --git a/gdb/doc/gdb.texinfo b/gdb/doc/gdb.texinfo
index 294276c..988eceb 100644
--- a/gdb/doc/gdb.texinfo
+++ b/gdb/doc/gdb.texinfo
@@ -18113,24 +18113,29 @@ The log stream contains debugging messages being produced by @value{GDBN}'s
 internals.
 @end table
 
-@node GDB/MI Out-of-band Records
-@subsection @sc{gdb/mi} Out-of-band Records
+@node GDB/MI Async Records
+@subsection @sc{gdb/mi} Async Records
 
-@cindex out-of-band records in @sc{gdb/mi}
-@cindex @sc{gdb/mi}, out-of-band records
-@dfn{Out-of-band} records are used to notify the @sc{gdb/mi} client of
+@cindex async records in @sc{gdb/mi}
+@cindex @sc{gdb/mi}, async records
+@dfn{Async} records are used to notify the @sc{gdb/mi} client of
 additional changes that have occurred.  Those changes can either be a
-consequence of @sc{gdb/mi} (e.g., a breakpoint modified) or a result of
+consequence of @sc{gdb/mi} commands (e.g., a breakpoint modified) or a result of
 target activity (e.g., target stopped).
 
-The following is a preliminary list of possible out-of-band records.
-In particular, the @var{exec-async-output} records.
+The following is the list of possible async records
 
 @table @code
 @item *stopped,reason="@var{reason}"
+The target has stopped.
+@item =thread-created,id="@var{id}"
+@item =thread-exited,id="@var{id}"
+A thread either was created, or has exited. The @var{id} field
+contains the @var{GDBN} identifier of the thread.
 @end table
 
-@var{reason} can be one of the following:
+For the @samp{*stopped} async record, the @var{reason} field can have
+one of the following values:
 
 @table @code
 @item breakpoint-hit
-- 
1.5.3.5


             reply	other threads:[~2008-04-26 17:44 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-04-26 17:54 Vladimir Prus [this message]
2008-04-26 19:05 ` Eli Zaretskii
2008-04-26 22:23   ` Vladimir Prus
2008-04-26 22:42     ` Eli Zaretskii

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=200804262144.03702.vladimir@codesourcery.com \
    --to=vladimir@codesourcery.com \
    --cc=gdb-patches@sources.redhat.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