From: Daniel Jacobowitz <drow@mvista.com>
To: gdb@sources.redhat.com
Subject: Re: lin-lwp.c and UltraSPARC
Date: Sat, 01 Nov 2003 00:47:00 -0000 [thread overview]
Message-ID: <20031101004707.GA12182@nevyn.them.org> (raw)
In-Reply-To: <1031031233150.ZM4663@localhost.localdomain>
On Fri, Oct 31, 2003 at 04:31:51PM -0700, Kevin Buettner wrote:
> On Oct 31, 9:38pm, Mark Kettenis wrote:
>
> > I'm also thinking about replacing the PTRACE_PEEKUSER with a
> > PTRACE_PEEKDATA since the latter should be implemented on all
> > architectures. In that case the call would probably fail the same way
> > on all architectures (assuming that nothing is mapped at address 0 on
> > all those architectures).
>
> This sounds like a good idea.
Yes, I agree. Interesting, this explains a number of pending Debian
bug reports... you could also PEEKDATA at an address that we expect to
be mapped. $sp might work.
--
Daniel Jacobowitz
MontaVista Software Debian GNU/Linux Developer
prev parent reply other threads:[~2003-11-01 0:47 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-10-31 20:38 Mark Kettenis
2003-10-31 23:31 ` Kevin Buettner
2003-11-01 0:47 ` Daniel Jacobowitz [this message]
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=20031101004707.GA12182@nevyn.them.org \
--to=drow@mvista.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