[PATCH with testcase] Bug 11568 - delete thread-specific breakpoint on the thread exit

[Pedro Alves]

On 07/31/2013 03:40 AM, Yao Qi wrote:
> The exit of thread 2 happens before thread 1 hits breakpoint on line 33. 
>   However, the order of 'thread 1 hits breakpoint' and 'GDB knows about 
> thread 2's exit' is not determined, in some runs (in async/non-stop 
> mode), I can get the fail below,

Hmm.  All-stop and non-stop behave different by design.  What's the
point of making an all-stop test work in non-stop?  async vs sync
is a different issue though -- that should be transparent.  Did you
mean just async?

-- 
Pedro Alves