From: Daniel Jacobowitz <drow@false.org>
To: Richard Henderson <rth@twiddle.net>
Cc: amodra@bigpond.net.au, gdb-patches@gcc.gnu.org
Subject: Re: ppc32 debugging ppc64, part 1
Date: Sat, 17 Sep 2005 21:24:00 -0000 [thread overview]
Message-ID: <20050917212403.GF8777@nevyn.them.org> (raw)
In-Reply-To: <20050912125047.GA5411@twiddle.net>
On Mon, Sep 12, 2005 at 05:50:47AM -0700, Richard Henderson wrote:
> This is just enough modifications to not immediately fail
> debugging a 64-bit process from a 32-bit debugger.
> * ppc-linux-nat.c (PTRACE_XFER_TYPE): Set to long.
You don't need this; PTRACE_TYPE_RET should work OK. We get that from
autoconf (even if the autoconf bits are a bit broken on Linux at the
moment, they'll choose long anyway).
> (ppc_register_u_addr): Compute wordsize correctly for 64-bit target.
> (ptrace_read_u, ptrace_write_u): New.
> (fetch_register): Simplify. Use PPC_PTRACE_PEEKUSR_3264 when needed.
> (store_register): Similarly with PPC_PTRACE_POKEUSR_3264.
> (default_xfer_partial, ppc32_linux_xfer_partial): New.
> (_initialize_ppc_linux_nat): Use them.
The rest of this I'm basically OK with, although it needs to go past
Kevin or Andrew.
I think it's safe to do away with the syscalls; the current userspace
ptrace interface where glibc has to special-case PEEKTEXT/PEEKDATA/PEEKUSER
is nasty enough, so I'm willing to declare glibc broken if it is ever
"fixed" to handle the PEEK*_3264 operations specially. Just my two
cents.
--
Daniel Jacobowitz
CodeSourcery, LLC
next prev parent reply other threads:[~2005-09-17 21:24 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-12 12:52 Richard Henderson
2005-09-12 19:47 ` Mark Kettenis
2005-09-12 20:32 ` Daniel Jacobowitz
2005-09-12 21:07 ` David S. Miller
2005-09-12 21:20 ` Mark Kettenis
2005-09-12 22:37 ` Richard Henderson
2005-09-12 23:20 ` Richard Henderson
2005-09-12 22:39 ` Richard Henderson
2005-09-17 21:24 ` Daniel Jacobowitz [this message]
2005-09-18 2:02 ` Richard Henderson
2005-09-18 2:14 ` 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=20050917212403.GF8777@nevyn.them.org \
--to=drow@false.org \
--cc=amodra@bigpond.net.au \
--cc=gdb-patches@gcc.gnu.org \
--cc=rth@twiddle.net \
/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