RE: Watchpoint conditions broken?

["Marc Khouzam" <marc dot khouzam at ericsson dot com>]

> 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().  
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 
for hardware breakpoints.

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

Does it make sense?

Index: gdb/breakpoint.c
===================================================================
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);
        }
 
-      if (reparse && b->cond_string != NULL)
+      if (b->cond_string != NULL)
        {
          char *s = b->cond_string;
          if (b->loc->cond)

==
Marc Khouzam