Re: RFC: MI output during program execution

Jim Ingham
2005-08-17T00:37:23Z

Note that for a truly asynchronous target, what you get is:

(gdb)
-exec-continue
^running
(gdb)
-exec-status
^done,status="running"
(gdb)
-exec-interrupt
^done,reason="signal-received",signal-name="SIGINT",signal-
meaning="Interrupt",thread-id="1"
(gdb)

Or something like that... So in that case the ^running really is the
equivalent of the ^done...

Jim

On Aug 16, 2005, at 5:26 PM, gdb-patches-digest-
help@sources.redhat.com wrote:

>
>
> Yeah - I'm beginning to think that we should use this:
>
> (gdb)
> -exec-continue
> *running
> ^done
> (gdb)
>
> Instead of the current:
>
> (gdb)
> -exec-continue
> ^running
> (gdb)
>
> It'd definitely have to be mi3 only, though! This would be a pretty
> big change that frontends would have to adapt to.
>
> The asymmetry between ^running and *stopped will bite us here. For
> instance, for a CLI command, I'd want roughly:
>
> (gdb)
> -interpreter-exec console "continue"
> *running
> ^done
> (gdb)
>
> Anyway, food for thought.
>
> --
> Daniel Jacobowitz
> CodeSourcery, LLC
>