linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: ashwin tanugula <ashwin.tanugula@gmail.com>
To: Brad Boyer <flar@allandria.com>
Cc: linuxppc-dev@ozlabs.org
Subject: Re: ptrace and ORIG_EAX on ppc
Date: Wed, 30 Mar 2005 14:15:17 -0500	[thread overview]
Message-ID: <838f7c5005033011157895e746@mail.gmail.com> (raw)
In-Reply-To: <20050330072558.GA13087@pants.nu>

On Tue, 29 Mar 2005 23:25:58 -0800, Brad Boyer <flar@allandria.com> wrote:
> On Tue, Mar 29, 2005 at 08:01:06PM -0500, ashwin tanugula wrote:
> > Hi!
> > Can somebody tell me how to set references to ORIG_EAX in ppc kernel.
> > We know ORIG_EAX is defined in unistd.h of i386. How do i make the
> > following program print two same pids in ppc?
> 
> The ORIG_EAX is a reference to a register as saved in the stack. The
> equivalent on ppc would seem to be PT_ORIG_R3. You're digging around
> in an area that is extremely non-portable. This program appears to
> be messing around with the syscall number before dispatch in the
> syscall table. The implementation of ptrace on ppc and ppc64
> explicitly does not allow changing this value, so I think you'll need
> to find a completely different way to achieve your desired result.
> 
> Just to lessen the confusion, what are you trying to accomplish? Not
> in the low-level detail sense, but what is the big picture goal?
> 
>         Brad Boyer
>         flar@allandria.com
> 
> 
Hi,
Thanks to Brad for his help.
ORIG_EAX has to be changed to PT_R0 not to PT_ORIG_R3.
The output i got after changing ORIG_EAX to PT_R0 is
root@slemieux:/home/ashwin # gcc ptrace_test.c
root@slemieux:/home/ashwin # ./a.out
Parent pid = 16682
getpid() returned 16682
getpid() returned 16682

--Ashwin.

      reply	other threads:[~2005-03-30 19:15 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-03-30  1:01 ptrace and ORIG_EAX on ppc ashwin tanugula
2005-03-30  7:25 ` Brad Boyer
2005-03-30 19:15   ` ashwin tanugula [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=838f7c5005033011157895e746@mail.gmail.com \
    --to=ashwin.tanugula@gmail.com \
    --cc=flar@allandria.com \
    --cc=linuxppc-dev@ozlabs.org \
    /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;
as well as URLs for NNTP newsgroup(s).