From: "Eli Zaretskii" <eliz@is.elta.co.il>
To: ac131313@cygnus.com
Cc: gdb@sources.redhat.com
Subject: Re: nm.h, *-nat.c and multi-arch?
Date: Wed, 04 Jul 2001 11:54:00 -0000 [thread overview]
Message-ID: <2561-Wed04Jul2001215136+0300-eliz@is.elta.co.il> (raw)
In-Reply-To: <3B4361F7.7040302@cygnus.com>
> Date: Wed, 04 Jul 2001 14:35:35 -0400
> From: Andrew Cagney <ac131313@cygnus.com>
>
> For instance, a hardware breakpoint mechanism implemented purely as
> register reads/writes shouldn't need to do anything like access ptrace()
> directly. Instead it should just access the target layer below it which
> (hopefully) is making available all the registers it needs.
Now I'm confused ;-) How can you access the debug registers except via
ptrace, procfs, etc.? Even DJGPP needs a bunch of system calls to do
that, since the debug registers are not directly accessible to DPMI
applications.
The last episode of the x86 watchpoint support was an attempt to
generalize the magic system calls used on various platforms to access
debug registers. But direct access to these registers is probably
possible only on embedded targets, where there's no OS to get in the
way.
next prev parent reply other threads:[~2001-07-04 11:54 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-07-04 9:12 Andrew Cagney
2001-07-04 10:28 ` Eli Zaretskii
2001-07-04 11:36 ` Andrew Cagney
2001-07-04 11:54 ` Eli Zaretskii [this message]
2001-07-04 10:43 ` Daniel Jacobowitz
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=2561-Wed04Jul2001215136+0300-eliz@is.elta.co.il \
--to=eliz@is.elta.co.il \
--cc=ac131313@cygnus.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