From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <gdb-return-31598-listarch-gdb=sources.redhat.com@sourceware.org>
Received: (qmail 7153 invoked by alias); 10 Apr 2008 03:07:06 -0000
Received: (qmail 6696 invoked by uid 22791); 10 Apr 2008 03:07:04 -0000
X-Spam-Check-By: sourceware.org
Received: from imr2.ericy.com (HELO imr2.ericy.com) (198.24.6.3)     by sourceware.org (qpsmtpd/0.31) with ESMTP; Thu, 10 Apr 2008 03:06:37 +0000
Received: from eusrcmw750.eamcs.ericsson.se (eusrcmw750.exu.ericsson.se [138.85.77.50]) 	by imr2.ericy.com (8.13.1/8.13.1) with ESMTP id m3A36Ylu014881 	for <gdb@sourceware.org>; Wed, 9 Apr 2008 22:06:35 -0500
Received: from ecamlmw720.eamcs.ericsson.se ([142.133.1.72]) by eusrcmw750.eamcs.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830); 	 Wed, 9 Apr 2008 22:06:34 -0500
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; 	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Subject: RE: Watchpoint conditions broken?
Date: Thu, 10 Apr 2008 14:17:00 -0000
Message-ID: <6D19CA8D71C89C43A057926FE0D4ADAA04E1BCCF@ecamlmw720.eamcs.ericsson.se>
References: <6D19CA8D71C89C43A057926FE0D4ADAA0429104B@ecamlmw720.eamcs.ericsson.se> <uy77magfq.fsf@gnu.org>
From: "Marc Khouzam" <marc.khouzam@ericsson.com>
To: "Eli Zaretskii" <eliz@gnu.org>
Cc: <gdb@sourceware.org>
X-IsSubscribed: yes
Mailing-List: contact gdb-help@sourceware.org; run by ezmlm
Precedence: bulk
List-Id: <gdb.sourceware.org>
List-Subscribe: <mailto:gdb-subscribe@sourceware.org>
List-Archive: <http://sourceware.org/ml/gdb/>
List-Post: <mailto:gdb@sourceware.org>
List-Help: <mailto:gdb-help@sourceware.org>, <http://sourceware.org/ml/#faqs>
Sender: gdb-owner@sourceware.org
X-SW-Source: 2008-04/txt/msg00080.txt.bz2


> Hardware watchpoints _are_ supposed to trigger, but once they do, GDB
> should see that the condition is false, and not announce the
> watchpoint.

That is what I needed to know.  Thanks.

I believe the problem is in update_watchpoint().=20=20
The below shows a fix that worked for me.
Funny thing is that this fix is the original way the code
was posted, as part of the patch about multiple locations=20
for hardware breakpoints.

http://sourceware.org/ml/gdb-patches/2007-12/msg00008.html

Does it make sense?

Index: gdb/breakpoint.c
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
RCS file: /cvs/src/src/gdb/breakpoint.c,v
retrieving revision 1.307
diff -u -r1.307 breakpoint.c
--- gdb/breakpoint.c    14 Mar 2008 18:57:43 -0000      1.307
+++ gdb/breakpoint.c    10 Apr 2008 02:57:41 -0000
@@ -986,7 +986,7 @@
            value_free (v);
        }
=20
-      if (reparse && b->cond_string !=3D NULL)
+      if (b->cond_string !=3D NULL)
        {
          char *s =3D b->cond_string;
          if (b->loc->cond)

=3D=3D
Marc Khouzam