|
From: Christian B. <bor...@de...> - 2011-01-12 09:31:44
|
Am 12.01.2011 10:19, schrieb Tom Hughes: > 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. This is pretty hacky, but cant we do the same thing in PRE(sys_execve)? |