From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 27263 invoked by alias); 9 Apr 2008 21:04:57 -0000 Received: (qmail 27253 invoked by uid 22791); 9 Apr 2008 21:04:56 -0000 X-Spam-Check-By: sourceware.org Received: from mtaout1.012.net.il (HELO mtaout1.012.net.il) (84.95.2.1) by sourceware.org (qpsmtpd/0.31) with ESMTP; Wed, 09 Apr 2008 21:04:37 +0000 Received: from HOME-C4E4A596F7 ([80.230.253.114]) by i-mtaout1.012.net.il (HyperSendmail v2007.08) with ESMTPA id <0JZ200K2NTU22200@i-mtaout1.012.net.il> for gdb@sourceware.org; Thu, 10 Apr 2008 00:18:02 +0300 (IDT) Date: Thu, 10 Apr 2008 09:16:00 -0000 From: Eli Zaretskii Subject: Re: Watchpoint conditions broken? In-reply-to: <6D19CA8D71C89C43A057926FE0D4ADAA0429104B@ecamlmw720.eamcs.ericsson.se> X-012-Sender: halo1@inter.net.il To: Marc Khouzam Cc: gdb@sourceware.org Reply-to: Eli Zaretskii Message-id: Content-transfer-encoding: 7BIT References: <6D19CA8D71C89C43A057926FE0D4ADAA0429104B@ecamlmw720.eamcs.ericsson.se> 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: 2008-04/txt/msg00079.txt.bz2 > Date: Wed, 9 Apr 2008 16:29:07 -0400 > From: "Marc Khouzam" > > I tried to investigate, but I couldn't figure out where the watchpoint condition > was actually checked after the watchpoint was hit... Or are hardware watchpoints > not supposed to be triggered at all, if the condition is not satisfied? Hardware watchpoints _are_ supposed to trigger, but once they do, GDB should see that the condition is false, and not announce the watchpoint. > Below is a very small tests that shows the problem. > This is not normal, right? No, it's a bug.