Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: "Eli Zaretskii" <eliz@is.elta.co.il>
To: muller@cerbere.u-strasbg.fr
Cc: gdb@sourceware.cygnus.com, dj@delorie.com
Subject: Re: x86 hardware breakpoint question
Date: Tue, 06 Nov 2001 12:54:00 -0000	[thread overview]
Message-ID: <2593-Fri16Nov2001184752+0200-eliz@is.elta.co.il> (raw)
In-Reply-To: <4.2.0.58.20011116135651.0128d658@ics.u-strasbg.fr> (message from Pierre Muller on Fri, 16 Nov 2001 14:07:07 +0100)

> Date: Fri, 16 Nov 2001 14:07:07 +0100
> From: Pierre Muller <muller@cerbere.u-strasbg.fr>
> Cc: gdb@sourceware.cygnus.com
> 
> At 20:26 15/11/2001 , Eli Zaretskii a \x7fcrit:
> > > Date: Thu, 15 Nov 2001 12:59:27 -0500
> > > From: Steven Bauer <bauer@atlas.lcs.mit.edu>
> > >
> > > Quick question, does gdb support hardware breakpoints on
> > > x86 architectures?
> >
> >Current GDB snapshots and the pretest of GDB 5.1 should support
> >them.  What version do you use and on what platform?
> But this depends on the TARGET OS:

Well, I did ask about the platform ;-)

>    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.


  reply	other threads:[~2001-11-16 16:47 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 [this message]
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
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=2593-Fri16Nov2001184752+0200-eliz@is.elta.co.il \
    --to=eliz@is.elta.co.il \
    --cc=dj@delorie.com \
    --cc=gdb@sourceware.cygnus.com \
    --cc=muller@cerbere.u-strasbg.fr \
    /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