This is the mail archive of the
gdb-patches@sources.redhat.com
mailing list for the GDB project.
Re: [RFC/RFA] Add hardware watchpoint support for cygwin target.
- From: "Eli Zaretskii" <eliz at is dot elta dot co dot il>
- To: muller at cerbere dot u-strasbg dot fr
- Cc: gdb-patches at sources dot redhat dot com
- Date: Wed, 28 Nov 2001 20:13:12 +0200
- Subject: Re: [RFC/RFA] Add hardware watchpoint support for cygwin target.
- References: <4.2.0.58.20011128183252.00acd198@ics.u-strasbg.fr>
- Reply-to: Eli Zaretskii <eliz at is dot elta dot co dot il>
> Date: Wed, 28 Nov 2001 18:44:44 +0100
> From: Pierre Muller <muller@cerbere.u-strasbg.fr>
>
> But te are some annoying things,
> the most annoying is that an exception seems to be generated
> on read access of the watched area even if you only set a normal
> watchpoint (which should use a write-only debug feature).
So you are saying that watch, rwatch, and awatch all yield the same
behavior?
Are you sure that you pass the watchpoint information correctly to
the OS? For example, is the format of DR7 as the OS wants it
identical to what GDB uses? The layout of bits in dr_control_mirror
follows Intel documentation, but the OS might want those bits in a
different format (that's what the corresponding DPMI call does, for
example). I don't have Windows docs, so I cannot check this.
> > /* Get the value of the DR6 debug status register from the inferior.
> > Here we just return the value stored in D_REGS, as we've got it
> > from the last go32_wait call. */
I believe you didn't really mean ``go32_wait'' here ;-)