From: muller@cerbere.u-strasbg.fr
To: DJ Delorie <dj@redhat.com>, cgf@redhat.com
Cc: gdb@sources.redhat.com
Subject: Re: x86 hardware breakpoint question
Date: Tue, 06 Nov 2001 17:12:00 -0000 [thread overview]
Message-ID: <3.0.6.32.20011117000436.00b05380@ics.u-strasbg.fr> (raw)
In-Reply-To: <200111162232.fAGMWsW02986@greed.delorie.com>
At 17:32 16/11/01 -0500, DJ Delorie wrote:
>
>> 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.
>
>SetThreadContext can set the hardware debug registers.
Did you try this out already ?
Because one of the problems that I got with my code
that uses VirtualProtectEx is that I can't change the
single step bit inside a system DLL (under win95 at least).
This forced me to add some complicated code,
that goes up the frame and sets a breakpoint at the first not
system DLL return address.
Outside system DLL I can single step over an
instruction that triggered the page protection
(momentantly disabling that protection) if
the address triggering the page protection is
not a watched address.
So I am surprised to hear that win32
lets you set debug registers, but if that works, great!
Are the debug registers process wide or
thread specific in that case ?
next prev parent reply other threads:[~2001-11-16 22:55 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
2001-11-06 15:58 ` DJ Delorie
2001-11-06 17:12 ` muller [this message]
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.20011117000436.00b05380@ics.u-strasbg.fr \
--to=muller@cerbere.u-strasbg.fr \
--cc=cgf@redhat.com \
--cc=dj@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