Re: MI: "^running" issues

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

Eli Zaretskii wrote:

>> From: Vladimir Prus <ghost@cs.msu.su>
>> Date: Wed, 5 Sep 2007 09:38:45 +0400
>> Cc: gdb@sources.redhat.com
>> 
>> >  >    - Killing the idea of async commands. It does not seem to be very
>> >  >    useful
>> >  > at this point, so we might be better off ripping it and implementing
>> >  > afresh later, when it's understood what they should be.
>> > 
>> > I'm working in the opposite direction: trying to get GDB to work
>> > asynchronously. I don't see the point of ripping out what is already
>> > there.
>> 
>> Then, can you please provide a specification of what "asynchronously"
>> means, and why it's good for users and frontends?
> 
> Asynchronous execution means that some GDB commands can be run while
> GDB waits for the target to stop.  It is good for users because you
> can do something useful while you wait for the target to stop.

Unfortunately, I never saw more concrete details. What commands are actually
meaningful to emit while target are running and are those commands of big
enough value to user to warrant extensive coding? Can interested parties document
those commands at GDB Wiki, or even in email?

- Volodya