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: Pedro Alves <palves at redhat dot com>
- To: Yao Qi <yao at codesourcery 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, 01 Aug 2013 11:51:03 +0100
- 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>
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