This is the mail archive of the
mailing list for the GDB project.
Re: Watching complex expressions patch
- To: Stan Shebs <shebs at cygnus dot com>
- Subject: Re: Watching complex expressions patch
- From: muller at cerbere dot u-strasbg dot fr
- Date: Thu, 04 Nov 1999 23:51:54 +0100
- Cc: gdb-patches at sourceware dot cygnus dot com
- References: <199911041058.LAA04309@cerbere.u-strasbg.fr>
At 11:50 04/11/99 -0800, Stan Shebs wrote:
> Date: Thu, 04 Nov 1999 11:46:19 +0100
> From: Pierre Muller <firstname.lastname@example.org>
> So my mecanism remembers the last memory that has been set a watch
> and after reject all watches of bigger memory regions including that
>I'm not clear on what you're getting at here, but it sounds wrong.
>GDB should allow the user to set any combination of watchpoints on the
>same or related pieces of data. The reason is the same as for
>breakpoints; it's possible to attach conditions to watchpoints, and
>you may have reason to attach one condition to "watch t.c", but a
>different condition to a "watch t". GDB should evaluate both
>conditions whenever t.c changes, but only one condition each time t.a
>or t.b changes.
No, you misunderstood me :
I was only talking about a val_clain for one specific watchpoint
Settings different watchpoint that overlap is not affected by my changes !!
The last memory region is reset to zero
for each watchpoint considered !