Tom Hughes 1a3f2889c8 The sloppyRXcheck logic in the sync checker was not correct - it was ...

simply treating R and X as equivalent but the real problem is that 
mappings can appear to have X permission entirely indepenent of anything
else with recent x86 kernels.

If a mapping is inside the (deliberately constrained) code segment then
it will appear to have X permission regardless of whether R or X was asked
for when it was mapped, so what we really need to do is allow the kernel
to add X to any mapping but not to take it away if we were expecting it.


git-svn-id: svn://svn.valgrind.org/valgrind/trunk@4985

2005-11-02 14:42:39 +00:00

..

aspacemgr.c

The sloppyRXcheck logic in the sync checker was not correct - it was

2005-11-02 14:42:39 +00:00

read_procselfmaps.c

Privatise parse_procselfmaps() and move it into aspacemgr.c in order

2005-09-28 09:37:16 +00:00