Re: [RFC] 07/10 non-stop inferior control

[Pedro Alves <pedro@codesourcery.com>]

A Wednesday 04 June 2008 12:49:06, Vladimir Prus wrote:
> Pedro Alves wrote:

> Am I missing something, or there's no way to interrupt all threads?
> Given that we have "continue -a"/"-exec-continue --all", I think a way
> to interrupt all threads will be desirable. In fact, I'd claim that if
> MI frontend has to issue several -exec-interrupt commands to stop the
> program completely, it's a regression in functionality. Of course, I
> can make MI do anything, but I need backend support for that :-)
>

Yes, you're right.  I had split the c -a into the other patch, because
I wanted to leave other interface extensions to be done incrementally,
and discurred `interrupt'.

> Also, it seems inconsistent to me that "continue" has the -a option,
> to resume all threads, while "interrupt" accepts an thread id. I'd
> suggest that "interrupt" be modified to accept -a, and not accept
> thread number.

I'll just do this, OK?

-- 
Pedro Alves