summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorVladimir Prus <vladimir@codesourcery.com>2010-02-12 10:34:47 +0000
committerVladimir Prus <vladimir@codesourcery.com>2010-02-12 10:34:47 +0000
commit3d0bdcd4069504b30e5e90dfb34ecc49bb8bc716 (patch)
tree5219b74c35bdf42bf66ca388d87217805f398bd3
parentb7783d93ed7e5b59b07b002e30ce65e074ec2f1f (diff)
downloadgdb-3d0bdcd4069504b30e5e90dfb34ecc49bb8bc716.tar.gz
* gdb.texinfo (GDB/MI Result Records): Clarify ^running.
-rw-r--r--gdb/doc/ChangeLog4
-rw-r--r--gdb/doc/gdb.texinfo9
2 files changed, 10 insertions, 3 deletions
diff --git a/gdb/doc/ChangeLog b/gdb/doc/ChangeLog
index b5bef2f5547..eb055e6b445 100644
--- 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 4fc064dda5c..d2fd7a82ca1 100644
--- 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