Re: RFC: MI output during program execution

Bob Rossi
2005-08-16T02:36:29Z

On Mon, Aug 15, 2005 at 08:33:11PM -0400, Daniel Jacobowitz wrote:
> On Mon, Aug 15, 2005 at 04:28:07PM +1200, Nick Roberts wrote:
> > > The hooks we were talking about were primarily for things like the
> > > breakpoint list and thread list. The ^running response is touchier.
> > > ^running is a result record, not an async record. It has to be the
> > > result of a command.
> >
> > It is classed as a result record in MI but presumably its an asynchronous
> > process. Perhaps it should be *running, just as it is *stopped. Treating it
>
> 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)

Agreed.

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

Agreed.

Bob Rossi