Re: [PATCH 16/30] Decouple target_interrupt from all-stop/non-stop modes

Pedro Alves
2016-03-21T18:24:39Z

On 03/21/2016 06:21 PM, Simon Marchi wrote:
> On 16-03-18 03:18 PM, Pedro Alves wrote:
>> In non-stop mode, "interrupt" results in a "stop with no mode, it
>> results in a remote interrupt request / stop with SIGINT. This is
>
> I don't really understand the first sentence, is there something missing?

Urgh, yes, looks like I deleted a line or something.
It should have read:

In non-stop mode, "interrupt" results in a "stop with no signal",
while in all-stop mode, it results in a remote interrupt
request / stop with SIGINT. This is (...)

>
>> currently implemented in both the Linux and remote target backends.
>> Move it to the core code instead, making target_interrupt specifically
>> always about "Interrupting as if with Ctrl-C", just like it is
>> documented.

Thanks,
Pedro Alves