public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: supriya kannery <supriyak@in.ibm.com>
To: David Miller <davem@davemloft.net>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Incorrect order of last two arguments of ptrace for requests PPC_PTRACE_GETREGS, SETREGS, GETFPREGS, SETFPREGS
Date: Fri, 27 Oct 2006 12:50:29 +0530	[thread overview]
Message-ID: <4541B33D.6090704@in.ibm.com> (raw)
In-Reply-To: <20061025.134354.92582918.davem@davemloft.net>

David Miller wrote:

>From: supriya kannery <supriyak@in.ibm.com>
>Date: Wed, 25 Oct 2006 16:23:14 +0530
>
>  
>
>>If we exchange the last two arguments like,
>>
>> ptrace (PPC_PTRACE_GETREGS, pid, &reg[0], 0);
>>
>>it works!
>>    
>>
>
>Please make sure that programs, such as gdb, aren't using the reversed
>argument order.  If they are, you cannot "fix" this as it will break
>all such applictions.
>  
>
David,
    I checked in gdb and ltrace code. None of them are using PPC_PTRACE* 
options to get register values.
Man page also doesn't mention these options. Once this is fixed, these 
options could be added to man page also.

Irrespective of whether we fix this, documentation of these options in 
manpage will clarify its usage I guess.
Thanks, Supriya

  reply	other threads:[~2006-10-27  7:08 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-10-25 10:53 Incorrect order of last two arguments of ptrace for requests PPC_PTRACE_GETREGS, SETREGS, GETFPREGS, SETFPREGS supriya kannery
2006-10-25 20:43 ` David Miller
2006-10-27  7:20   ` supriya kannery [this message]
2006-10-27  7:10     ` David Miller
2006-10-31 12:18       ` supriya kannery
2006-11-22 18:36 ` David Woodhouse
2006-11-22 21:35   ` Benjamin Herrenschmidt
2006-12-04 21:58   ` Anton Blanchard
2007-04-30  5:42     ` Paul Mackerras

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=4541B33D.6090704@in.ibm.com \
    --to=supriyak@in.ibm.com \
    --cc=davem@davemloft.net \
    --cc=linux-kernel@vger.kernel.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