From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 4138 invoked by alias); 16 Nov 2001 21:40:40 -0000 Mailing-List: contact gdb-help@sourceware.cygnus.com; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-owner@sources.redhat.com Received: (qmail 4024 invoked from network); 16 Nov 2001 21:40:35 -0000 Received: from unknown (HELO factorix.sdv.fr) (194.206.196.2) by sourceware.cygnus.com with SMTP; 16 Nov 2001 21:40:35 -0000 Received: from ordimaison (ip-76-210.evc.net [212.95.76.210]) by factorix.sdv.fr (8.11.4/8.11.4) with SMTP id fAGLAhm04038; Fri, 16 Nov 2001 22:10:43 +0100 Message-Id: <3.0.6.32.20011116224941.00fe0750@ics.u-strasbg.fr> X-Sender: muller@ics.u-strasbg.fr X-Mailer: QUALCOMM Windows Eudora Light Version 3.0.6 (32) Date: Tue, 06 Nov 2001 15:15:00 -0000 To: Christopher Faylor , gdb@sources.redhat.com From: muller@cerbere.u-strasbg.fr Subject: Re: x86 hardware breakpoint question In-Reply-To: <20011116205455.GA18328@redhat.com> References: <2593-Fri16Nov2001184752+0200-eliz@is.elta.co.il> <20011115125927.B3449@atlas.lcs.mit.edu> <20011115125927.B3449@atlas.lcs.mit.edu> <4.2.0.58.20011116135651.0128d658@ics.u-strasbg.fr> <2593-Fri16Nov2001184752+0200-eliz@is.elta.co.il> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" X-SW-Source: 2001-11/txt/msg00067.txt.bz2 At 15:54 16/11/01 -0500, Christopher Faylor wrote: >On Fri, Nov 16, 2001 at 06:47:52PM +0200, Eli Zaretskii wrote: >>> cygwin that completely relies on win32 API calls does not support >>> hardware breakpoint (nor watchpoints) >>> because there is no API call to set a hardware trap. >> >>I think this is just because no one implemented Cygwin support for the >>new facilities on i386-nat.c. When this was discussed a few months >>ago, someone, I think DJ Delorie, posted a list of Win32 API entries >>that support hardware watchpoints and breakpoints. > >I can't find this, Eli. Can you provide any clues on what to look for? >I'd like to have hardware brekpoints into cygwin if I can. I had pseudo-hardware watchpoints working using the page protection mechanisms available with the VirtualXXX functions. I am trying to get up to date my old code that added "hardware" watchpoints with VirtualProtectEx. As soon as this works correctly again, I will send a patch, even if my code is far from optimal, because otherwise it will again get lost in confilcts with future changes...