From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 953 invoked by alias); 11 Oct 2006 22:06:47 -0000 Received: (qmail 939 invoked by uid 22791); 11 Oct 2006 22:06:46 -0000 X-Spam-Check-By: sourceware.org Received: from sibelius.xs4all.nl (HELO brahms.sibelius.xs4all.nl) (82.92.89.47) by sourceware.org (qpsmtpd/0.31) with ESMTP; Wed, 11 Oct 2006 22:06:43 +0000 Received: from elgar.sibelius.xs4all.nl (root@elgar.sibelius.xs4all.nl [192.168.0.2]) by brahms.sibelius.xs4all.nl (8.13.8/8.13.6) with ESMTP id k9BM68sS029833; Thu, 12 Oct 2006 00:06:08 +0200 (CEST) Received: from elgar.sibelius.xs4all.nl (kettenis@localhost.sibelius.xs4all.nl [127.0.0.1]) by elgar.sibelius.xs4all.nl (8.13.8/8.13.6) with ESMTP id k9BM68gd018269; Thu, 12 Oct 2006 00:06:08 +0200 (CEST) Received: (from kettenis@localhost) by elgar.sibelius.xs4all.nl (8.13.8/8.13.8/Submit) id k9BM68ml030875; Thu, 12 Oct 2006 00:06:08 +0200 (CEST) Date: Wed, 11 Oct 2006 22:06:00 -0000 Message-Id: <200610112206.k9BM68ml030875@elgar.sibelius.xs4all.nl> From: Mark Kettenis To: drow@false.org CC: andrew.stubbs@st.com, gdb-patches@sourceware.org In-reply-to: <20061011135545.GA26060@nevyn.them.org> (message from Daniel Jacobowitz on 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> <20061011135545.GA26060@nevyn.them.org> 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/msg00130.txt.bz2 > Date: Wed, 11 Oct 2006 09:55:45 -0400 > From: Daniel Jacobowitz > > 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. I don't see the problem either. Mark