OpenE2K
/
binutils-gdb
12
0
Fork 0
Code Issues Pull Requests Releases Wiki Activity

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

This commit is contained in:
Vladimir Prus 2010-02-12 10:34:47 +00:00
parent e4782e8381
commit 8e9c5e020f
2 changed files with 10 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
gdb/doc/ChangeLog
View File

@ -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

9
gdb/doc/gdb.texinfo
View File

@ -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