From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 18946 invoked by alias); 20 Oct 2006 17:42:36 -0000 Received: (qmail 18934 invoked by uid 22791); 20 Oct 2006 17:42:35 -0000 X-Spam-Check-By: sourceware.org Received: from heller.inter.net.il (HELO heller.inter.net.il) (192.114.186.73) by sourceware.org (qpsmtpd/0.31) with ESMTP; Fri, 20 Oct 2006 17:42:30 +0000 Received: from HOME-C4E4A596F7 (IGLD-80-230-33-81.inter.net.il [80.230.33.81]) by heller.inter.net.il (MOS 3.7.3a-GA) with ESMTP id ATR00377 (AUTH halo1); Fri, 20 Oct 2006 18:38:39 +0200 (IST) Date: Fri, 20 Oct 2006 17:42:00 -0000 Message-Id: From: Eli Zaretskii To: Daniel Jacobowitz CC: andrew.stubbs@st.com, gdb-patches@sourceware.org In-reply-to: <20061020142933.GA28396@nevyn.them.org> (message from Daniel Jacobowitz on Fri, 20 Oct 2006 10:29:33 -0400) Subject: Re: [PATCH] Don't give spurious warnings when using thread specific breakpoints Reply-to: Eli Zaretskii References: <452CF534.4060209@st.com> <20061011135545.GA26060@nevyn.them.org> <452D0385.6010103@st.com> <20061011204525.GA9622@nevyn.them.org> <45361793.1020202@st.com> <20061018141419.GA7771@nevyn.them.org> <4536444C.9020709@st.com> <45374981.5080304@st.com> <20061020142933.GA28396@nevyn.them.org> X-IsSubscribed: yes Mailing-List: contact gdb-patches-help@sourceware.org; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-patches-owner@sourceware.org X-SW-Source: 2006-10/txt/msg00255.txt.bz2 > Date: Fri, 20 Oct 2006 10:29:33 -0400 > From: Daniel Jacobowitz > Cc: Andrew STUBBS , 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.)