This is the mail archive of the
gdb-patches@sourceware.org
mailing list for the GDB project.
Re: [PATCH] Don't give spurious warnings when using thread specific breakpoints
- From: Daniel Jacobowitz <drow at false dot org>
- To: Andrew STUBBS <andrew dot stubbs at st dot com>
- Cc: GDB Patches <gdb-patches at sourceware dot org>
- Date: Wed, 11 Oct 2006 09:55:45 -0400
- Subject: Re: [PATCH] Don't give spurious warnings when using thread specific breakpoints
- References: <452CF534.4060209@st.com>
On Wed, Oct 11, 2006 at 02:44:20PM +0100, Andrew STUBBS wrote:
> When creating a thread specific breakpoint GDB will warn about other
> breakpoints set on the same address even when they are specific to
> another thread.
>
> The attached patch prevents it warning about breakpoints from other
> threads. When a non-thread specific breakpoint is created, or already
> exists, the warning is still given, but is annotated with the thread
> information. When not using thread specific breakpoints the behaviour
> should remain unaltered.
(gdb) b main if 1
Breakpoint 1 at 0x439ee0
(gdb) b main if 2
Note: breakpoint 1 also set at pc 0x439ee0.
Breakpoint 2 at 0x439ee0
If that's right, why is similar for threads wrong? That's just a
different condition. And the wording is such that it's perfectly
correct.
--
Daniel Jacobowitz
CodeSourcery