Thread (5 messages) 5 messages, 5 authors, 2007-04-30

Re: Incorrect order of last two arguments of ptrace for requests PPC_PTRACE_GETREGS, SETREGS, GETFPREGS, SETFPREGS

From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
Date: 2006-11-22 21:36:53
Also in: lkml

On Wed, 2006-11-22 at 18:36 +0000, David Woodhouse wrote:
On
quoted
This is because PPC_PTRACE_GETREGS option for powerpc is implemented 
such that general purpose
registers of the child process get copied to the address variable 
instead of data variable. Same is
the case with other PPC request options PPC_PTRACE_SETREGS, GETFPREGS 
and SETFPREGS.

Prepared a patch for this problem and tested with 2.6.18-rc6 kernel. 
This patch can be applied directly to 2.6.19-rc3 kernel.
A more appropriate place to send this would be the linux-ppc development
list.
Also it's possible that existing code like gcc relies on that "feature"
no ?

Ben.
 
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help