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

[Eli Zaretskii <eliz@gnu.org>]

> Date: Fri, 20 Oct 2006 10:29:33 -0400
> From: Daniel Jacobowitz <drow@false.org>
> Cc: Andrew STUBBS <andrew.stubbs@st.com>, gdb-patches@sourceware.org
> 
> This is a construct which can not, to the best of my knowledge, be
> usefully translated.

Sure, it can.

> (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

We need to have different code branches, one each for each one of the
possibilities, and each branch should have a format string for a full
sentence that is produced by that branch.

If there are too many such possible combinations, then the i18n
comment should explain the context, as I mentioned elsewhere.  (I'm
quite sure we've been through a similar discussion a year or so ago,
about another place where the code does similar things.)