* gdb.texinfo (GDB/MI Result Records): Clarify ^running.

diff --git a/gdb/doc/ChangeLog b/gdb/doc/ChangeLog
index b5bef2f554772a602b778d22d276c6388a0c11d8..eb055e6b445ccb044838a3aa5e2b38b486543733 100644 (file)
--- a/gdb/doc/ChangeLog
+++ b/gdb/doc/ChangeLog
@@ -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

diff --git a/gdb/doc/gdb.texinfo b/gdb/doc/gdb.texinfo
index 4fc064dda5c767a11e1a2f2dc6525d4a86e56acf..d2fd7a82ca1644cf85137cc04cd79901586ce749 100644 (file)
--- a/gdb/doc/gdb.texinfo
+++ b/gdb/doc/gdb.texinfo
@@ -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