From: Chris Faylor <cgf@cygnus.com>
To: gdb@sourceware.cygnus.com
Subject: Re: About unified debug register handling for i386 CPU.
Date: Wed, 06 Sep 2000 10:10:00 -0000 [thread overview]
Message-ID: <20000906130917.B13889@cygnus.com> (raw)
In-Reply-To: <200009060608.CAA06709@indy.delorie.com>
On Wed, Sep 06, 2000 at 02:08:10AM -0400, Eli Zaretskii wrote:
>> Remember also that the win32 API does not support
>> hardware debug registers
>
>Really? So you cannot have hardware-assisted debugging in Win32
>applications?
I am not aware of any way to do this with the Win32 debugging API
but I'd be thrilled to be proved wrong.
cgf
next prev parent reply other threads:[~2000-09-06 10:10 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20000901192328.A28312@valinux.com>
[not found] ` <200009041047.LAA10659@phal.cygnus.co.uk>
2000-09-04 8:49 ` gdb doesn't work very well with dynamic linked binaries H . J . Lu
2000-09-04 10:52 ` Mark Kettenis
2000-09-04 11:11 ` Daniel Berlin
2000-09-04 11:22 ` Ulrich Drepper
[not found] ` <drepper@redhat.com>
2000-09-05 19:12 ` Kevin Buettner
2000-09-04 16:45 ` H . J . Lu
2000-09-04 22:49 ` Eli Zaretskii
2000-09-04 23:32 ` H . J . Lu
2000-09-05 3:36 ` Eli Zaretskii
2000-09-05 6:34 ` Mark Kettenis
2000-09-05 8:47 ` Eli Zaretskii
2000-09-05 17:06 ` Mark Kettenis
2000-09-05 22:52 ` Eli Zaretskii
2000-09-05 8:49 ` H . J . Lu
2000-09-05 18:23 ` Stan Shebs
2000-09-05 18:33 ` H . J . Lu
2000-09-05 22:54 ` Eli Zaretskii
2000-09-05 8:44 ` H . J . Lu
2000-09-05 18:02 ` Stan Shebs
2000-09-05 20:45 ` H . J . Lu
2000-09-05 22:55 ` Eli Zaretskii
2000-10-14 23:09 ` Andrew Cagney
2000-09-05 22:53 ` Eli Zaretskii
[not found] ` <3.0.6.32.20000906001339.00b0ae90@idefix.wisa.be>
2000-09-05 23:08 ` About unified debug register handling for i386 CPU Eli Zaretskii
2000-09-06 10:10 ` Chris Faylor [this message]
2000-09-06 4:55 Pierre Muller
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=20000906130917.B13889@cygnus.com \
--to=cgf@cygnus.com \
--cc=gdb@sourceware.cygnus.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).