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: Jim Blandy <jimb at zwingli dot cygnus dot com>
- Subject: Re: Problems with hardware watchpoint on ia32.
- From: Eli Zaretskii <eliz at delorie dot com>
- Date: Wed, 22 Mar 2000 13:06:33 -0500 (EST)
- CC: 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>
- Reply-to: Eli Zaretskii <eliz at is dot elta dot co dot il>
> Eli's test of the value's type is incorrect if the watch expression
> contains a structure comparison, like (foo == bar) || (something
> else), where foo and bar are structures. In that case, there will be
> a value of type "struct", not at the end of the value list, but which
> should be watched in its entirety.
Errr... do you have an actual example program where this happens?
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?
In case it matters, I tested this with a DJGPP-compiled program; DJGPP
by default uses COFF debugging info.