Re: [doc] clarify MI ^running

[Vladimir Prus <vladimir@codesourcery.com>]

[-- Attachment #1: Type: text/plain, Size: 210 bytes --]

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

[-- Attachment #2: running.diff --]
[-- Type: text/x-patch, Size: 1431 bytes --]

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  <vladimir@codesourcery.com>
+
+	* gdb.texinfo (GDB/MI Result Records): Clarify ^running.
+
 2010-02-10  Tom Tromey  <tromey@redhat.com>
 
 	* 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