Inadvertently run inferior threads

[Pedro Alves]

On 06/15/2015 06:56 PM, Pedro Alves wrote:

> That's why I said:
> ~~~
> So that should mean that even for GNU/Linux, it should be possible
> to end in the exact same, when any thread other than the one that we
> had started the infcall in reports an event that doesn't cause a stop.
> E.g., a thread specific breakpoint, a "handle nostop" signal, etc.
> ~~~
> 
> And I just confirmed it, with a thread-specific breakpoint that
> trips on the wrong thread, thus, reporting a trap to the core,
> which does not cause a user-visible stop, and then ends up
> marking all threads running when we gdb internally re-resumes
> the program.  Like so:
> 

(...)

FYI, I've converted this to a proper testsuite test, and am
playing with potential fixes.

Thanks,
Pedro Alves