Valgrind on stable grsec

Discuss usability issues, general maintenance, and general support issues for a grsecurity-enabled system.

Valgrind on stable grsec

Postby cmouse » Thu Oct 07, 2010 10:56 am

execve("/usr/lib/valgrind/memcheck-amd64-linux", ["/usr/bin/valgrind.bin"], [/*
39 vars */]) = 0
open("/proc/self/maps", O_RDONLY) = 3
read(3, "38000000-381f5000 r-xp 00000000 "..., 100000) = 549
read(3, "", 99451) = 0
close(3) = 0
mmap(0x402001000, 4194304, PROT_READ|PROT_WRITE|PROT_EXEC,
MAP_PRIVATE|MAP_FIXED|MAP_ANONYMOUS, 0, 0) = -1 EPERM (Operation not permitted)
getpid() = 27233

When trying to start valgrind on grsec enabled machine. Any ideas why this fails?
cmouse
 
Posts: 98
Joined: Tue Dec 17, 2002 10:58 am

Re: Valgrind on stable grsec

Postby spender » Thu Oct 07, 2010 11:35 am

It's the new MPROTECT behavior to reject RWX mappings instead of silently demoting them to RW. You'll have to turn off mprotect on the valgrind binary.

-Brad
spender
 
Posts: 2185
Joined: Wed Feb 20, 2002 8:00 pm


Return to grsecurity support