This is the mail archive of the gdb-patches@sourceware.org mailing list for the GDB project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

[RFA] [doc] thread-created/thread-exited


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


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]