On 15 Nov 2007 at 12:30, Christian Parpart wrote: > On Wednesday 14 November 2007 23:45:01 [EMAIL PROTECTED] wrote: > > valgrind generates code at runtime therefore its binaries need paxctl -m, > > in fact i thought the ebuild was already doing that... > > paxctl -m /usr/lib64/valgrind/amd64-linux/memcheck > > just running `paxctl -m /usr/bin/valgrind doesn't do the trick obviousely, > the above works fine for me, thanks for the hint though :)
that's why i said 'binaries' not 'binary' ;). also if you look at the PaX log, it'll tell you the exact binary on which you have to change the flags. -- [EMAIL PROTECTED] mailing list
