Re: Inadvertently run inferior threads

On 06/10/2015 04:13 PM, Eli Zaretskii wrote:
>> Date: Sat, 14 Mar 2015 16:55:58 +0200
>> From: Eli Zaretskii <[email protected]>
>> Cc: [email protected]
>>
>>> Otherwise, "(gdb) interrupt" would probably work.
>>
>> Thanks, I will try using this next time.
> 
> It seems like 'interrupt' does nothing in native debugging of a target
> that doesn't support async execution, at least on MS-Windows.  Is that
> a bug, or is it expected?

It's old code, but I think the idea of the target_can_async check
in interrupt_command is "this shouldn't even be possible".  If the
target doesn't support async execution, you're not supposed to
be able to end up with a prompt while the target is running
in the first place.

Thanks,
Pedro Alves