diff options
author | Eli Zaretskii <eliz@gnu.org> | 2000-08-16 08:03:43 +0000 |
---|---|---|
committer | Eli Zaretskii <eliz@gnu.org> | 2000-08-16 08:03:43 +0000 |
commit | d7491b3f51c983dba510568ce2f142a15663b65c (patch) | |
tree | 8017a8387c9af558244d680625eab9ea2069e30a /gdb/value.h | |
parent | 31612ca61ad1b6f671cae51eef0872c4bf3ad6bf (diff) | |
download | ppe42-binutils-d7491b3f51c983dba510568ce2f142a15663b65c.tar.gz ppe42-binutils-d7491b3f51c983dba510568ce2f142a15663b65c.zip |
* value.h (struct value) <lazy>: Add a comment about its use for
watchpoints.
Diffstat (limited to 'gdb/value.h')
-rw-r--r-- | gdb/value.h | 13 |
1 files changed, 12 insertions, 1 deletions
diff --git a/gdb/value.h b/gdb/value.h index e87582e579..b0f1c63c26 100644 --- 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. */ |