Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Richard Henderson <rth@redhat.com>
To: Richard Henderson <rth@twiddle.net>
Cc: Mark Kettenis <mark.kettenis@xs4all.nl>,
	drow@false.org, amodra@bigpond.net.au, gdb-patches@gcc.gnu.org
Subject: Re: ppc32 debugging ppc64, part 1
Date: Mon, 12 Sep 2005 23:20:00 -0000	[thread overview]
Message-ID: <20050912232025.GA14993@redhat.com> (raw)
In-Reply-To: <20050912223637.GA3587@twiddle.net>

On Mon, Sep 12, 2005 at 03:36:37PM -0700, Richard Henderson wrote:
> But for the record, I was seeing odd things and wanted to get the
> libc code out of the way.  I later discovered the typo in my own
> code, but I never got around to reverting the use of syscall.

Oh, yes, one could in fact argue that libc is broken.  It doesn't
handle the PTRACE_PEEK*_3264 commands specially, as it does with
PTRACE_PEEK*.  So you'd have to write 

  if (cmd == *_3264)
    ptrace (cmd, tid, addr, buf)
  else
    *buf = ptrace (cmd, tid, addr, 0);

... and then rely on libc never being fixed.  And in this case I
don't see what going through libc buys us besides frustration.



r~


  reply	other threads:[~2005-09-12 23:20 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 [this message]
2005-09-12 22:39   ` Richard Henderson
2005-09-17 21:24 ` Daniel Jacobowitz
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=20050912232025.GA14993@redhat.com \
    --to=rth@redhat.com \
    --cc=amodra@bigpond.net.au \
    --cc=drow@false.org \
    --cc=gdb-patches@gcc.gnu.org \
    --cc=mark.kettenis@xs4all.nl \
    --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