On Wednesday 14 November 2007 23:45:01 [EMAIL PROTECTED] wrote: > On 14 Nov 2007 at 17:42, Christian Parpart wrote: > > well... how could i (ideally) get in gerneral rid of such errors without > > loosing the hardened profile or hardened-sources kernel? > > 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 :) regards, Christian Parpart.
signature.asc
Description: This is a digitally signed message part.
