From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 8776 invoked by alias); 27 Mar 2005 02:56:50 -0000 Mailing-List: contact gdb-patches-help@sources.redhat.com; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-patches-owner@sources.redhat.com Received: (qmail 8762 invoked from network); 27 Mar 2005 02:56:44 -0000 Received: from unknown (HELO lakermmtao09.cox.net) (68.230.240.30) by sourceware.org with SMTP; 27 Mar 2005 02:56:44 -0000 Received: from white ([68.9.64.121]) by lakermmtao09.cox.net (InterMail vM.6.01.04.00 201-2131-118-20041027) with ESMTP id <20050327025643.RJFY28448.lakermmtao09.cox.net@white>; Sat, 26 Mar 2005 21:56:43 -0500 Received: from bob by white with local (Exim 3.35 #1 (Debian)) id 1DFOs5-0000AO-00; Sat, 26 Mar 2005 22:55:29 -0500 Date: Sun, 27 Mar 2005 02:56:00 -0000 From: Bob Rossi To: Eli Zaretskii Cc: gdb-patches@sources.redhat.com Subject: Re: [mi] organize possible exec async mi oc command reasons Message-ID: <20050327035529.GA581@white> Mail-Followup-To: Eli Zaretskii , gdb-patches@sources.redhat.com References: <20050324154602.GA10558@white> <01c530ab$Blat.v2.4$de96e8e0@zahav.net.il> <20050324210231.GA10808@white> <01c531ef$Blat.v2.4$d2dbeba0@zahav.net.il> <01c53207$Blat.v2.4$edd75800@zahav.net.il> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <01c53207$Blat.v2.4$edd75800@zahav.net.il> User-Agent: Mutt/1.3.28i X-SW-Source: 2005-03/txt/msg00356.txt.bz2 On Sat, Mar 26, 2005 at 03:29:05PM +0200, Eli Zaretskii wrote: > > Date: Sat, 26 Mar 2005 12:36:32 +0200 > > From: "Eli Zaretskii" > > > > Btw, do we always have @var{reason} after "stopped"? If not, then > > it's optional and should be inside [...]. > > In addition, it looks to me like "stopped" states the reason like so: > > *stopped,reason="REASON" > > If this is true, then the first @table in the section we are talking > about should say > > @table @code > @item > *stopped,reason="@var{reason}" > @end table Hi Eli, Thanks for all the excellent suggestions, I can see how this is much much nicer than what I had. There is probably still room for improving, what do you think? BTW, you might already know, but it's worth mentioning, there are 3 types of out-of-band records. In this section only the *stopped, which is exec-async-output, is mentioned. That's why I added the sentence, +In particular, the @var{exec-async-output} records. After this doco and patch is approved, I'm going to enumerate the other 2 case's, status-async-output and notify-async-output. Also, For each item, I could add the MI commands that could be done to get the response described. Like, -exec-finish produces function-finished. However, the user won't know when you get 'read-watchpoint-trigger'. What do you think? and if so, how would that fit into this description? Another table perhaps? Thanks, Bob Rossi 2005-03-26 Bob Rossi * gdb.texinfo (GDB/MI Out-of-band Records): Enumerating the possible out-of-band exec-async-output reasons. Index: gdb.texinfo =================================================================== RCS file: /cvs/src/src/gdb/doc/gdb.texinfo,v retrieving revision 1.233 diff -w -u -r1.233 gdb.texinfo --- gdb.texinfo 10 Mar 2005 13:12:33 -0000 1.233 +++ gdb.texinfo 27 Mar 2005 02:50:34 -0000 @@ -15416,9 +15416,40 @@ 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. @table @code -@item "*" "stop" +@item *stopped,reason="@var{reason}" +@end table + +@var{reason} can be one of the following: + +@table @code +@item breakpoint-hit +A breakpoint was reached. +@item watchpoint-trigger +A watchpoint was triggered. +@item read-watchpoint-trigger +A read watchpoint was triggered +@item access-watchpoint-trigger +An access watchpoint was triggered. +@item function-finished +An -exec-finish or similar CLI command was accomplished. +@item location-reached +An -exec-until or similar CLI command was accomplished. +@item watchpoint-scope +A watchpoint has gone out of scope. +@item end-stepping-range +An -exec-next,-exec-next-instruction,-exec-step,-exec-step-instruction or +similar CLI command was accomplished. +@item exited-signalled +The inferior exited because of a signal. +@item exited +The inferior exited. +@item exited-normally +The inferior exited normally. +@item signal-received +A signal was received by the inferior. @end table