Re: [PATCH] Don't give spurious warnings when using thread specific breakpoints

[Daniel Jacobowitz <drow@false.org>]

On Fri, Oct 20, 2006 at 08:10:37AM +0200, Eli Zaretskii wrote:
> > No, you misunderstand the code. There can be an arbitrary number 
> > breakpoints, each of which can have zero, one or two annotations, and 
> > they are all presented as one message.
> 
> I was trying to give an example, so the question is: did I succeed to
> explain how to resolve these issues?  If not, please show me several
> examples of the output that this code produces now, and I will modify
> my counter-example accordingly.

This is a construct which can not, to the best of my knowledge, be
usefully translated.  Which is a shame.  Try this:

(gdb) b main
Breakpoint 1 at 0x439ee0
(gdb) b main
Note: breakpoint 1 also set at pc 0x439ee0.
Breakpoint 2 at 0x439ee0
(gdb) b main
Note: breakpoints 1 and 2 also set at pc 0x439ee0.
Breakpoint 3 at 0x439ee0
(gdb) disable 2
(gdb) b main
Note: breakpoints 1, 2 (disabled) and 3 also set at pc 0x439ee0.
Breakpoint 4 at 0x439ee0

-- 
Daniel Jacobowitz
CodeSourcery