From 8e9c5e020f5fa7b76a1f6694e2eb00a1585151cc Mon Sep 17 00:00:00 2001 From: Vladimir Prus Date: Fri, 12 Feb 2010 10:34:47 +0000 Subject: [PATCH] * gdb.texinfo (GDB/MI Result Records): Clarify ^running. --- gdb/doc/ChangeLog | 4 ++++ gdb/doc/gdb.texinfo | 9 ++++++--- 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 + + * gdb.texinfo (GDB/MI Result Records): Clarify ^running. + 2010-02-10 Tom Tromey * 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 -- 2.30.2