From: Michael Snyder <msnyder@cygnus.com>
To: John Hughes <john@Calva.COM>
Cc: Eli Zaretskii <eliz@is.elta.co.il>, gdb-patches@sourceware.cygnus.com
Subject: Re: Hardware watchpoints for UnixWare; based on snapshot 20010627
Date: Fri, 29 Jun 2001 14:15:00 -0000 [thread overview]
Message-ID: <3B3CEFD9.9E9221C1@cygnus.com> (raw)
In-Reply-To: <CDENKKMHIFMALMCCKPCFGEEGCAAA.john@Calva.COM>
John Hughes wrote:
>
> Eli Zaretskii writes:
> > From: "John Hughes" <john@Calva.COM>
> >> Interface between procfs.c and i386v42-nat.c is unclean,
> >> but I don't see how to do it better.
> >
> > Is there something that i386-nat.c could do to help?
>
> I don't realy see how. The problem is that
>
> 1. the "i386v42mp-nat.c" (what a foul name!) code needs access to
> the debug registers stored in the "pr_family" part of the
> prstatus.pr_lwp structure, which is only known to procfs.c
>
> 2. It also needs to issue a PCSDBREG command via procfs.
>
> So it needs some horrid special access to stuff only procfs knows.
How about adding access methods to procfs.c explicitly
to export this functionality to i386*-nat.c? I seem to
recall we already have a few like that, and IMO it is
better than many alternatives.
next prev parent reply other threads:[~2001-06-29 14:15 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-06-29 1:52 John Hughes
2001-06-29 4:16 ` Eli Zaretskii
2001-06-29 5:14 ` John Hughes
2001-06-29 5:32 ` Eli Zaretskii
2001-06-29 5:44 ` John Hughes
2001-06-29 14:15 ` Michael Snyder [this message]
2001-07-02 6:07 ` John Hughes
2001-07-02 11:57 ` Michael Snyder
2001-07-03 12:28 ` Andrew Cagney
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=3B3CEFD9.9E9221C1@cygnus.com \
--to=msnyder@cygnus.com \
--cc=eliz@is.elta.co.il \
--cc=gdb-patches@sourceware.cygnus.com \
--cc=john@Calva.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