* gdb.texinfo (GDB/MI Result Records): Clarify ^running.
This commit is contained in:
parent
e4782e8381
commit
8e9c5e020f
2 changed files with 10 additions and 3 deletions
|
@ -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>
|
2010-02-10 Tom Tromey <tromey@redhat.com>
|
||||||
|
|
||||||
* gdb.texinfo (Debugging Output): Document set debug parser and
|
* gdb.texinfo (Debugging Output): Document set debug parser and
|
||||||
|
|
|
@ -22059,9 +22059,12 @@ values.
|
||||||
|
|
||||||
@item "^running"
|
@item "^running"
|
||||||
@findex ^running
|
@findex ^running
|
||||||
@c Is this one correct? Should it be an out-of-band notification?
|
This result record is equivalent to @samp{^done}. Historically, it
|
||||||
The asynchronous operation was successfully started. The target is
|
was output instead of @samp{^done} if the command has resumed the
|
||||||
running.
|
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"
|
@item "^connected"
|
||||||
@findex ^connected
|
@findex ^connected
|
||||||
|
|
Loading…
Reference in a new issue