Re: [Valgrind-users] Valgrind cannot start

[Aki T. <cm...@de...>]

On Thu, Oct 07, 2010 at 12:21:57PM +0200, WAROQUIERS Philippe wrote:
> 
> At work, we encountered 'not enough memory' crashes of our big
> application
> under valgrind due to the way the superblocks are managed (see bug
> http://bugs.kde.org/show_bug.cgi?id=250101
> (there is a proposed patch to solve this bug)
> 
> However, in your case, not being able to even allocate about 20 Mb
> ((14.3Mb + 4.2 Mb) looks really strange :
> 
> >==10577==
> >==10577==     Valgrind's memory management: out of memory:
> >==10577==        newSuperblock's request for 4194304 bytes failed.
> >==10577==        14356480 bytes have already been allocated.
> >==10577==     Valgrind cannot continue.  Sorry.
> 
> 
> So, it is unclear what is happening. Maybe the best is to enable
> the debug traces of valgrind to have more details.
> If still not clear, strace of valgrind might give even more details
> about the system calls leading to the above failure.
> 
> Philippe
> 

Should've though strace myself. The problem is 

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

This is probably due to grsecurity kernel but I am not sure why, it has worked 
before on a 32 bit system. 

Aki Tuomi