Re: MI: asynchronous operation details

[Vladimir Prus <ghost@cs.msu.su>]

On Tuesday 22 November 2005 17:00, Bob Rossi wrote:

> > > You could interupt the inferior, to tell it to stop. I think that would
> > > be equivalent to typing ^c at the console now.
> >
> > Well, exactly. I can do "^C" today, so nothing gained at all.
>
> Well, clearly sending the ^C is not as nice as the MI -exec-interrupt
> command. The former is simply legacy from a console driven front end.
> It's not intuitive.

Yes, just a bit.

> > > I'm sure there are other useful features also.
> >
> > Still curious what are they ;-)
>
> If you look in the documentation, the 'Asynchronous command.' will be
> next to each command that is supposed to support an asynchronous style
> command. For example:
>
>     -exec-interrupt

Except for "interrupt", other occurences are for various flavours of "run" -- 
continue/next/nexti/step/stepi/unti/finish. So, it still looks like 
"-exec-interrupt" is the only command that can be meaningfully issued while 
inferior is running.

- Volodya