Julian Seward writes:

> After some futzing around it appears that
> the mechanism works for ppc32-linux and ppc64-linux for kernel 2.6.20
> but fails in some bizarre way on 2.6.23.  
> 
> So now I'm wondering if ptrace handling on ppc platforms has also
> been made more paranoid, or otherwise changed, lately?  Do you know?

There were a bunch of ptrace changes for ppc/ppc64 that went in to
2.6.23, in part to allow gdb to restart system calls properly after
executing a function in the child.  There was also some consolidation
of the code for PEEKDATA and POKEDATA into generic code.  The only
thing that I know of where we made things more paranoid is that ptrace
used to be able to change FE0/1 in the MSR on 64-bit platforms (but
not 32-bit), which is is now not allowed (if you set them this way,
the change wouldn't stick anyway).

It's certainly possible that we broke something along the way.  Do you
have anything more specific about which ptrace call is failing or
misbehaving, and in what way?

Paul.

-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2005.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
Valgrind-developers mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/valgrind-developers

Reply via email to