|
From: Tom H. <to...@co...> - 2011-01-12 09:33:14
|
On 12/01/11 09:31, Christian Borntraeger wrote: > 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)? Well sure, I was just trying to give me a workaround. There is a question here about how far we should go though - it will very quickly get out of control if we try and make every call that deals with filenames cope with this. Tom -- Tom Hughes (to...@co...) http://compton.nu/ |