|
From: <kei...@te...> - 2006-02-03 00:07:19
|
I ran valgrind on the application which has 59 child processes. What I=20 found out was that it costs more than 6 times VM (e.g. 3378068 kB)=20 than running the application without valgrind. So, I guess we would be happier if valgrind can trace one specific=20 process that we are interested in. Does anyone know how to deal with this? Please, help. Thanks, Keishi Sonoda |
|
From: Paul P. <ppl...@gm...> - 2006-02-03 03:46:28
|
On 2/2/06, kei...@te... <kei...@te...> wrote: > > So, I guess we would be happier if valgrind can trace one specific > process that we are interested in. One way that I have dealt with this: # assume foo is the specific binary of interest, and is exec()ed # by some other binary. mv foo foo.exe cat > foo <<"EOF" #!/bin/sh exec valgrind <VG-options, if any> foo.exe "$@" EOF chmod +x foo If the processes all run the same executable, the same shell wrapper could be extended to trigger VG execution depending on command line arguments, environment variables, etc. Cheers, |