Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
* Re: [doc] clarify MI ^running
@ 2010-02-12  9:11 Vladimir Prus
  2010-02-12 10:11 ` Eli Zaretskii
  2010-02-12 16:48 ` Tom Tromey
  0 siblings, 2 replies; 4+ messages in thread
From: Vladimir Prus @ 2010-02-12  9:11 UTC (permalink / raw)
  To: gdb-patches; +Cc: vladimir

[-- Attachment #1: Type: text/plain, Size: 210 bytes --]

On Friday 12 February 2010 09:10:49 you wrote:

> 
> This patches updates documentation to accurately explain what the ^running
> result record in MI supposed to mean now. OK?

And here's the patch.

- Volodya

[-- Attachment #2: running.diff --]
[-- Type: text/x-patch, Size: 1431 bytes --]

Index: ChangeLog
===================================================================
RCS file: /cvs/src/src/gdb/doc/ChangeLog,v
retrieving revision 1.1006
diff -u -p -r1.1006 ChangeLog
--- ChangeLog	10 Feb 2010 18:57:21 -0000	1.1006
+++ ChangeLog	12 Feb 2010 06:09:04 -0000
@@ -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
Index: gdb.texinfo
===================================================================
RCS file: /cvs/src/src/gdb/doc/gdb.texinfo,v
retrieving revision 1.667
diff -u -p -r1.667 gdb.texinfo
--- gdb.texinfo	10 Feb 2010 18:57:21 -0000	1.667
+++ gdb.texinfo	12 Feb 2010 06:09:06 -0000
@@ -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

^ permalink raw reply	[flat|nested] 4+ messages in thread

* Re: [doc] clarify MI ^running
  2010-02-12  9:11 [doc] clarify MI ^running Vladimir Prus
@ 2010-02-12 10:11 ` Eli Zaretskii
  2010-02-12 16:48 ` Tom Tromey
  1 sibling, 0 replies; 4+ messages in thread
From: Eli Zaretskii @ 2010-02-12 10:11 UTC (permalink / raw)
  To: Vladimir Prus; +Cc: gdb-patches, vladimir

> From: Vladimir Prus <vladimir@codesourcery.com>
> Date: Fri, 12 Feb 2010 12:10:54 +0300
> Cc: vladimir@codesourcery.com
> 
> On Friday 12 February 2010 09:10:49 you wrote:
> 
> > 
> > This patches updates documentation to accurately explain what the ^running
> > result record in MI supposed to mean now. OK?
> 
> And here's the patch.

This is okay, thanks.


^ permalink raw reply	[flat|nested] 4+ messages in thread

* Re: [doc] clarify MI ^running
  2010-02-12  9:11 [doc] clarify MI ^running Vladimir Prus
  2010-02-12 10:11 ` Eli Zaretskii
@ 2010-02-12 16:48 ` Tom Tromey
  1 sibling, 0 replies; 4+ messages in thread
From: Tom Tromey @ 2010-02-12 16:48 UTC (permalink / raw)
  To: Vladimir Prus; +Cc: gdb-patches

>>>>> "Volodya" == Vladimir Prus <vladimir@codesourcery.com> writes:

Volodya> +This result record is equivalent to @samp{^done}.  Historically, it
Volodya> +was output instead of @samp{^done} if the command has resumed the
Volodya> +target.  This behaviour is maintained for backward compatibility, but

I think it should read "if the command had resumed".

Tom


^ permalink raw reply	[flat|nested] 4+ messages in thread

* [doc] clarify MI ^running
@ 2010-02-12  6:10 Vladimir Prus
  0 siblings, 0 replies; 4+ messages in thread
From: Vladimir Prus @ 2010-02-12  6:10 UTC (permalink / raw)
  To: gdb-patches


This patches updates documentation to accurately explain what the ^running
result record in MI supposed to mean now. OK?

- Volodya


^ permalink raw reply	[flat|nested] 4+ messages in thread

end of thread, other threads:[~2010-02-12 16:48 UTC | newest]

Thread overview: 4+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2010-02-12  9:11 [doc] clarify MI ^running Vladimir Prus
2010-02-12 10:11 ` Eli Zaretskii
2010-02-12 16:48 ` Tom Tromey
  -- strict thread matches above, loose matches on Subject: below --
2010-02-12  6:10 Vladimir Prus

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox