From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 9983 invoked by alias); 26 Apr 2008 17:44:24 -0000 Received: (qmail 9974 invoked by uid 22791); 26 Apr 2008 17:44:24 -0000 X-Spam-Check-By: sourceware.org Received: from mail.codesourcery.com (HELO mail.codesourcery.com) (65.74.133.4) by sourceware.org (qpsmtpd/0.31) with ESMTP; Sat, 26 Apr 2008 17:44:06 +0000 Received: (qmail 6865 invoked from network); 26 Apr 2008 17:44:04 -0000 Received: from unknown (HELO localhost) (vladimir@127.0.0.2) by mail.codesourcery.com with ESMTPA; 26 Apr 2008 17:44:04 -0000 From: Vladimir Prus Date: Sat, 26 Apr 2008 17:54:00 -0000 Subject: [RFA] [doc] thread-created/thread-exited To: gdb-patches@sources.redhat.com X-TUID: 06681b511d3ef409 X-Length: 2055 X-UID: 168 MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200804262144.03702.vladimir@codesourcery.com> Mailing-List: contact gdb-patches-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-patches-owner@sourceware.org X-SW-Source: 2008-04/txt/msg00603.txt.bz2 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