This is the mail archive of the
gdb-patches@sourceware.org
mailing list for the GDB project.
Re: [PATCH with testcase] Bug 11568 - delete thread-specific breakpoint on the thread exit
- From: Yao Qi <yao at codesourcery dot com>
- To: Pedro Alves <palves at redhat dot com>
- Cc: Muhammad Waqas <mwaqas at codesourcery dot com>, <gdb-patches at sourceware dot org>, <tromey at redhat dot com>, <ali_anwar at codesourcery dot com>
- Date: Thu, 1 Aug 2013 18:58:41 +0800
- Subject: Re: [PATCH with testcase] Bug 11568 - delete thread-specific breakpoint on the thread exit
- References: <51F619CE dot 5040407 at codesourcery dot com> <51F633E5 dot 7000302 at codesourcery dot com> <51F65519 dot 2080806 at codesourcery dot com> <51F67992 dot 30704 at codesourcery dot com> <51F7967E dot 3060900 at codesourcery dot com> <51F8791A dot 1090704 at codesourcery dot com> <51FA3D97 dot 6040400 at redhat dot com>
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.
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.
--
Yao (éå)