1 |
On 15 Nov 2007 at 12:30, Christian Parpart wrote: |
2 |
|
3 |
> On Wednesday 14 November 2007 23:45:01 pageexec@××××××××.hu wrote: |
4 |
> > valgrind generates code at runtime therefore its binaries need paxctl -m, |
5 |
> > in fact i thought the ebuild was already doing that... |
6 |
> |
7 |
> paxctl -m /usr/lib64/valgrind/amd64-linux/memcheck |
8 |
> |
9 |
> just running `paxctl -m /usr/bin/valgrind doesn't do the trick obviousely, |
10 |
> the above works fine for me, thanks for the hint though :) |
11 |
|
12 |
that's why i said 'binaries' not 'binary' ;). also if you look at the |
13 |
PaX log, it'll tell you the exact binary on which you have to change |
14 |
the flags. |
15 |
|
16 |
-- |
17 |
gentoo-hardened@g.o mailing list |