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 20:09:43 +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> <51FA3F61 dot 8040802 at codesourcery dot com> <51FA4619 dot 8010006 at redhat dot com>
On 08/01/2013 07:27 PM, Pedro Alves wrote:
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.
OK, I am fine with it. Then, I withdraw my comment on adding a
breakpoint command 'info threads' in the breakpoint on line 33. It is
in this mail <http://sourceware.org/ml/gdb-patches/2013-07/msg00805.html>
--
Yao (éå)