| 1 |
On Wednesday 14 November 2007 23:45:01 pageexec@××××××××.hu wrote: |
| 2 |
> On 14 Nov 2007 at 17:42, Christian Parpart wrote: |
| 3 |
> > well... how could i (ideally) get in gerneral rid of such errors without |
| 4 |
> > loosing the hardened profile or hardened-sources kernel? |
| 5 |
> |
| 6 |
> valgrind generates code at runtime therefore its binaries need paxctl -m, |
| 7 |
> in fact i thought the ebuild was already doing that... |
| 8 |
|
| 9 |
paxctl -m /usr/lib64/valgrind/amd64-linux/memcheck |
| 10 |
|
| 11 |
just running `paxctl -m /usr/bin/valgrind doesn't do the trick obviousely, |
| 12 |
the above works fine for me, thanks for the hint though :) |
| 13 |
|
| 14 |
regards, |
| 15 |
Christian Parpart. |
Archives