This is the mail archive of the
gdb-patches@sourceware.cygnus.com
mailing list for the GDB project.
Re: Problems with hardware watchpoint on ia32.
- To: Eli Zaretskii <eliz at is dot elta dot co dot il>
- Subject: Re: Problems with hardware watchpoint on ia32.
- From: Jim Blandy <jimb at zwingli dot cygnus dot com>
- Date: 27 Mar 2000 15:26:16 -0500
- Cc: Jim Blandy <jimb at cygnus dot com>, hjl at lucon dot org, gdb at sourceware dot cygnus dot com, gdb-patches at sourceware dot cygnus dot com
- References: <20000307132401.A20282@valinux.com><200003081008.FAA16481@indy.delorie.com><20000308084304.A3150@lucon.org><200003091210.HAA19857@indy.delorie.com><npya7c6zn7.fsf@zwingli.cygnus.com><200003221806.NAA14225@indy.delorie.com>
> I seem to be unable to reproduce the problem, at least in a C program:
> whenever I say "watch foo == bar" (where foo and bar are structs), GDB
> curses thusly:
>
> Structure has no component named operator==.
>
> Am I missing something?
As Michael points out, structure comparison is broken. But that
doesn't change my original point --- that it's perfectly legitimate to
have `struct value' objects representing structures, which should be
watched in their entirety.
The type of a value is irrelevant --- we're trying to track the memory
references made in the course of evaluating the expression.