diff options
| author | Vladimir Prus <vladimir@codesourcery.com> | 2010-02-12 10:34:47 +0000 |
|---|---|---|
| committer | Vladimir Prus <vladimir@codesourcery.com> | 2010-02-12 10:34:47 +0000 |
| commit | 8e9c5e020f5fa7b76a1f6694e2eb00a1585151cc (patch) | |
| tree | 6ff03138a7f47dafcab8d3a6d3608351b0da748d | |
| parent | e4782e838130706e2d2d53a9e3c29f71419863ae (diff) | |
| download | gdb-8e9c5e020f5fa7b76a1f6694e2eb00a1585151cc.zip gdb-8e9c5e020f5fa7b76a1f6694e2eb00a1585151cc.tar.gz gdb-8e9c5e020f5fa7b76a1f6694e2eb00a1585151cc.tar.bz2 | |
* gdb.texinfo (GDB/MI Result Records): Clarify ^running.
| -rw-r--r-- | gdb/doc/ChangeLog | 4 | ||||
| -rw-r--r-- | gdb/doc/gdb.texinfo | 9 |
2 files changed, 10 insertions, 3 deletions
diff --git a/gdb/doc/ChangeLog b/gdb/doc/ChangeLog index b5bef2f..eb055e6 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 4fc064d..d2fd7a8 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 |