From: muller@cerbere.u-strasbg.fr
To: Christopher Faylor <cgf@redhat.com>, gdb@sources.redhat.com
Subject: Re: x86 hardware breakpoint question
Date: Tue, 06 Nov 2001 15:15:00 -0000 [thread overview]
Message-ID: <3.0.6.32.20011116224941.00fe0750@ics.u-strasbg.fr> (raw)
In-Reply-To: <20011116205455.GA18328@redhat.com>
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...
next prev parent reply other threads:[~2001-11-16 21:40 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-11-04 14:28 Steven Bauer
2001-11-05 6:38 ` Eli Zaretskii
2001-11-05 23:28 ` Pierre Muller
2001-11-06 12:54 ` Eli Zaretskii
2001-11-06 14:35 ` Christopher Faylor
2001-11-06 15:15 ` muller [this message]
2001-11-06 15:58 ` DJ Delorie
2001-11-06 17:12 ` muller
2001-11-06 18:13 ` DJ Delorie
2001-11-06 19:34 ` Christopher Faylor
2001-11-07 18:38 ` muller
2001-11-05 8:25 ` Quality Quorum
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=3.0.6.32.20011116224941.00fe0750@ics.u-strasbg.fr \
--to=muller@cerbere.u-strasbg.fr \
--cc=cgf@redhat.com \
--cc=gdb@sources.redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox