From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 2387 invoked by alias); 12 Feb 2010 09:11:05 -0000 Received: (qmail 2371 invoked by uid 22791); 12 Feb 2010 09:11:04 -0000 X-SWARE-Spam-Status: No, hits=-2.4 required=5.0 tests=AWL,BAYES_00,SPF_PASS X-Spam-Check-By: sourceware.org Received: from mail.codesourcery.com (HELO mail.codesourcery.com) (38.113.113.100) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Fri, 12 Feb 2010 09:10:58 +0000 Received: (qmail 9532 invoked from network); 12 Feb 2010 09:10:57 -0000 Received: from unknown (HELO wind.localnet) (vladimir@127.0.0.2) by mail.codesourcery.com with ESMTPA; 12 Feb 2010 09:10:57 -0000 To: gdb-patches@sourceware.org Subject: Re: [doc] clarify MI ^running From: Vladimir Prus Date: Fri, 12 Feb 2010 09:11:00 -0000 Cc: vladimir@codesourcery.com MIME-Version: 1.0 Content-Type: Multipart/Mixed; boundary="Boundary-00=_esRdLPlB76sMuez" Message-Id: <201002121210.54299.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: 2010-02/txt/msg00319.txt.bz2 --Boundary-00=_esRdLPlB76sMuez Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Content-length: 210 On Friday 12 February 2010 09:10:49 you wrote: > > This patches updates documentation to accurately explain what the ^running > result record in MI supposed to mean now. OK? And here's the patch. - Volodya --Boundary-00=_esRdLPlB76sMuez Content-Type: text/x-patch; charset="utf-8"; name="running.diff" Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename="running.diff" Content-length: 1431 Index: ChangeLog =================================================================== RCS file: /cvs/src/src/gdb/doc/ChangeLog,v retrieving revision 1.1006 diff -u -p -r1.1006 ChangeLog --- ChangeLog 10 Feb 2010 18:57:21 -0000 1.1006 +++ ChangeLog 12 Feb 2010 06:09:04 -0000 @@ -1,3 +1,7 @@ +2010-02-12 Vladimir Prus + + * gdb.texinfo (GDB/MI Result Records): Clarify ^running. + 2010-02-10 Tom Tromey * gdb.texinfo (Debugging Output): Document set debug parser and Index: gdb.texinfo =================================================================== RCS file: /cvs/src/src/gdb/doc/gdb.texinfo,v retrieving revision 1.667 diff -u -p -r1.667 gdb.texinfo --- gdb.texinfo 10 Feb 2010 18:57:21 -0000 1.667 +++ gdb.texinfo 12 Feb 2010 06:09:06 -0000 @@ -22059,9 +22059,12 @@ values. @item "^running" @findex ^running -@c Is this one correct? Should it be an out-of-band notification? -The asynchronous operation was successfully started. The target is -running. +This result record is equivalent to @samp{^done}. Historically, it +was output instead of @samp{^done} if the command has resumed the +target. This behaviour is maintained for backward compatibility, but +all frontends should treat @samp{^done} and @samp{^running} +identically and rely on the @samp{*running} output record to determine +which threads are resumed. @item "^connected" @findex ^connected --Boundary-00=_esRdLPlB76sMuez--