From: Andrew Cagney <ac131313@cygnus.com>
To: Mark Kettenis <kettenis@science.uva.nl>
Cc: eliz@is.elta.co.il, msnyder@cygnus.com, gdb-patches@sources.redhat.com
Subject: Re: [PATCH]: Make Linux use the new unified x86 watchpoint support
Date: Tue, 27 Mar 2001 10:03:00 -0000 [thread overview]
Message-ID: <3AC0D5D9.1D61585A@cygnus.com> (raw)
In-Reply-To: <200103270911.f2R9BX421793@debye.wins.uva.nl>
Mark Kettenis wrote:
>
> Date: Tue, 27 Mar 2001 08:55:00 +0200 (IST)
> From: Eli Zaretskii <eliz@is.elta.co.il>
>
> On Mon, 26 Mar 2001, Michael Snyder wrote:
>
> > Guys, this implementation has problems. You have it hard-coded
> > so that on a linux host, it unconditionally calls native linux
> > methods involving ptrace to get the debug registers. This breaks
> > very badly if you're using a native linux host to debug a remote
> > i386 target.
>
> Just like the old implementation. I suspect the old implementation
> just happened to work because it didn't do any strict error checking.
>
> The fundamental problem is that the watpoint-stuff isn't part of the
> target vector.
I think it is a combination of both the architecture and the target
vector. It is the same problem as software single step. A layer of the
target is asked to implement a memory watch. Since that can't be
implemented directly, it asks the architecture vector to implement it
for it.
Andrew
next prev parent reply other threads:[~2001-03-27 10:03 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-03-21 18:47 Mark Kettenis
2001-03-26 18:14 ` Michael Snyder
2001-03-27 0:46 ` Mark Kettenis
2001-03-27 8:45 ` Michael Snyder
2001-04-17 17:26 ` Michael Snyder
2001-04-17 23:58 ` Mark Kettenis
2001-03-26 18:35 ` Michael Snyder
2001-03-26 22:57 ` Eli Zaretskii
2001-03-27 1:13 ` Mark Kettenis
2001-03-27 1:31 ` Eli Zaretskii
2001-03-27 2:09 ` Mark Kettenis
2001-03-27 2:20 ` Eli Zaretskii
2001-03-27 10:58 ` Mark Salter
2001-03-28 1:19 ` Eli Zaretskii
2001-03-28 5:10 ` Mark Salter
2001-03-28 5:39 ` Eli Zaretskii
2001-03-28 8:06 ` Mark Salter
2001-03-29 12:06 ` Eli Zaretskii
2001-03-29 12:03 ` Mark Salter
2001-03-27 8:55 ` Michael Snyder
2001-03-27 9:46 ` Eli Zaretskii
2001-03-27 9:55 ` Fernando Nasser
2001-03-27 11:59 ` Michael Snyder
2001-03-27 12:04 ` Fernando Nasser
2001-03-27 11:58 ` Michael Snyder
2001-03-28 1:31 ` Eli Zaretskii
2001-03-28 2:03 ` Mark Kettenis
2001-03-27 8:52 ` Michael Snyder
2001-03-27 15:51 ` Mark Kettenis
2001-03-27 10:03 ` Andrew Cagney [this message]
2001-03-27 8:48 ` Michael Snyder
2001-03-27 9:43 ` Eli Zaretskii
2001-03-27 11:57 ` Michael Snyder
2001-03-28 1:30 ` Eli Zaretskii
2001-03-28 11:53 ` Michael Snyder
2001-03-29 12:06 ` Eli Zaretskii
[not found] <Pine.SUN.3.91.1010329160617.4915G-100000@is>
2001-03-29 18:15 ` Mark Salter
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=3AC0D5D9.1D61585A@cygnus.com \
--to=ac131313@cygnus.com \
--cc=eliz@is.elta.co.il \
--cc=gdb-patches@sources.redhat.com \
--cc=kettenis@science.uva.nl \
--cc=msnyder@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