* value.h (struct value) <lazy>: Add a comment about its use for

        watchpoints.

diff --git a/gdb/ChangeLog b/gdb/ChangeLog
index ecbdde402a33d531a0f89006315dc6df76a47ff1..7e4e6fe50a20a44caf1653cae8b565d49aa739a1 100644 (file)
--- a/gdb/ChangeLog
+++ b/gdb/ChangeLog
@@ -1,3 +1,8 @@
+2000-08-16  Eli Zaretskii <eliz@is.elta.co.il>
+
+       * value.h (struct value) <lazy>: Add a comment about its use for
+        watchpoints.
+
 2000-08-12  Kevin Buettner  <kevinb@redhat.com>
 
        * cxux-nat.c (fetch_inferior_registers): Protoize.

diff --git a/gdb/value.h b/gdb/value.h
index e87582e579c76bb36f6e570167c91a93ecec2102..b0f1c63c26c658677352f3253da19be28f45ed9a 100644 (file)
--- a/gdb/value.h
+++ b/gdb/value.h
@@ -97,7 +97,18 @@ struct value
     /* If zero, contents of this value are in the contents field.
        If nonzero, contents are in inferior memory at address
        in the location.address field plus the offset field
-       (and the lval field should be lval_memory).  */
+       (and the lval field should be lval_memory).
+
+       WARNING: This field is used by the code which handles
+       watchpoints (see breakpoint.c) to decide whether a particular
+       value can be watched by hardware watchpoints.  If the lazy flag
+       is set for some member of a value chain, it is assumed that
+       this member of the chain doesn't need to be watched as part of
+       watching the value itself.  This is how GDB avoids watching the
+       entire struct or array when the user wants to watch a single
+       struct member or array element.  If you ever change the way
+       lazy flag is set and reset, be sure to consider this use as
+       well!  */
     char lazy;
     /* If nonzero, this is the value of a variable which does not
        actually exist in the program.  */