From mboxrd@z Thu Jan 1 00:00:00 1970 From: "Eli Zaretskii" To: muller@cerbere.u-strasbg.fr Cc: gdb-patches@sources.redhat.com Subject: Re: [RFC/RFA] Add hardware watchpoint support for cygwin target. Date: Wed, 28 Nov 2001 10:13:00 -0000 Message-id: <8011-Wed28Nov2001201312+0200-eliz@is.elta.co.il> References: <4.2.0.58.20011128183252.00acd198@ics.u-strasbg.fr> X-SW-Source: 2001-11/msg00539.html > Date: Wed, 28 Nov 2001 18:44:44 +0100 > From: Pierre Muller > > 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 ;-) From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 8626 invoked by alias); 28 Nov 2001 18:13:54 -0000 Mailing-List: contact gdb-patches-help@sourceware.cygnus.com; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-patches-owner@sources.redhat.com Received: (qmail 8593 invoked from network); 28 Nov 2001 18:13:47 -0000 Received: from unknown (HELO frigg.inter.net.il) (192.114.186.16) by hostedprojects.ges.redhat.com with SMTP; 28 Nov 2001 18:13:47 -0000 Received: from zaretsky ([192.116.55.139]) by frigg.inter.net.il (Mirapoint) with ESMTP id BBR14015; Wed, 28 Nov 2001 20:13:38 +0200 (IST) Date: Sat, 17 Nov 2001 16:07:00 -0000 From: "Eli Zaretskii" To: muller@cerbere.u-strasbg.fr Message-ID: <8011-Wed28Nov2001201312+0200-eliz@is.elta.co.il> X-Mailer: emacs 21.1.50 (via feedmail 8 I) and Blat ver 1.8.9 CC: gdb-patches@sources.redhat.com In-reply-to: <4.2.0.58.20011128183252.00acd198@ics.u-strasbg.fr> (message from Pierre Muller on Wed, 28 Nov 2001 18:44:44 +0100) Subject: Re: [RFC/RFA] Add hardware watchpoint support for cygwin target. Reply-to: Eli Zaretskii References: <4.2.0.58.20011128183252.00acd198@ics.u-strasbg.fr> X-SW-Source: 2001-11/txt/msg00324.txt.bz2 Message-ID: <20011117160700.MJ400lvJIiLIv3VW6dk-LAqGunR2ONIbPUiFcolRV84@z> > Date: Wed, 28 Nov 2001 18:44:44 +0100 > From: Pierre Muller > > 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 ;-)