From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 7388 invoked by alias); 14 Aug 2007 19:41:21 -0000 Received: (qmail 7278 invoked by uid 22791); 14 Aug 2007 19:41:21 -0000 X-Spam-Check-By: sourceware.org Received: from romy.inter.net.il (HELO romy.inter.net.il) (213.8.233.24) by sourceware.org (qpsmtpd/0.31) with ESMTP; Tue, 14 Aug 2007 19:41:16 +0000 Received: from HOME-C4E4A596F7 (IGLD-83-130-248-51.inter.net.il [83.130.248.51]) by romy.inter.net.il (MOS 3.7.3-GA) with ESMTP id IQE85363 (AUTH halo1); Tue, 14 Aug 2007 22:41:01 +0300 (IDT) Date: Tue, 14 Aug 2007 19:41:00 -0000 Message-Id: From: Eli Zaretskii To: luisgpm@linux.vnet.ibm.com CC: gdb@sourceware.org In-reply-to: <1187108458.4388.14.camel@localhost> (message from Luis Machado on Tue, 14 Aug 2007 13:20:58 -0300) Subject: Re: Watchpoints stopping GDB on specific threads Reply-to: Eli Zaretskii References: <1187108458.4388.14.camel@localhost> X-IsSubscribed: yes Mailing-List: contact gdb-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-owner@sourceware.org X-SW-Source: 2007-08/txt/msg00115.txt.bz2 > From: Luis Machado > Date: Tue, 14 Aug 2007 13:20:58 -0300 > > I'm looking forward to have the same functionality for watchpoints. So > whenever GDB detects a watchpoint trigger, it would verify the current > thread and would stop only if the thread matches the ID we provided in a > command like "watch
thread ". if no ID is provided, GDB > would stop at every thread as usual (assuming a threaded watchpoint > support). Unless I misunderstand something fundamental, if the current thread ID is in some variable, you could define a condition for a watchpoint, no?