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

Pedro Alves
2013-08-01T11:27:34Z

On 08/01/2013 11:58 AM, Yao Qi wrote:
> On 08/01/2013 06:51 PM, Pedro Alves wrote:
>> 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
>
> Pedro,
> Is it an all-stop test? I think it should work on both all-stop and
> non-stop.

Then it should explicitly test both modes. Say, move the body
to a procedure, and call it twice. Running the gdb.threads/
tests with forced non-stop mode really makes no sense.

>> is a different issue though -- that should be transparent. Did you
>> mean just async?
>
> I meant async + non-stop. I get one fail from time to time when I run
> the test with async on and non-stop on. I run the test with async on
> only, but can't get one fail in ten runs.

--
Pedro Alves