|
From: Tom H. <to...@co...> - 2011-01-12 09:19:45
|
On 12/01/11 09:05, Konstantin Serebryany wrote: > The failure happens when chrome tries to fork/exec itself via > /proc/self/exe link. > This sounds unfriendly to valgrind, since /proc/self/exe points to > memcheck instead of chrome. Right? > Any suggestion how to workaround this (other than > removing /proc/self/exe from the chrome source code)? If it did readlink(/proc/self/exe) and then exec'ed the result it would work as valgrind traps the readlink and returns a path to the real executable. Tom -- Tom Hughes (to...@co...) http://compton.nu/ |