|
From: Daniel L. <dan...@sb...> - 2008-10-23 09:44:26
|
Hello, I want to capture the output from valgrind to valgrind_log.txt. However, the command: valgrind --log-file=valgrind_log.txt --num-callers=25 ./Test/bin/gcc-4.1.1/debug/test >> testing_valgrind.txt creates valgrind_log.txt.29297 (as well as testing_valgrind.txt of course). This effectively makes it impossible for me to process the output from a script operation, as the process id changes every time. Why does valgrind do this? Can I turn off the prefix? georog-dev:/home/buildbot/trunk/GFL> valgrind --version valgrind-3.2.3-Debian Thanks in advance! -- Daniel Lidström |
|
From: Julian S. <js...@ac...> - 2008-10-23 10:14:46
|
Either use --log-file-exactly= or upgrade to 3.3.1, which has a different and more flexible scheme for logfile naming. J On Thursday 23 October 2008, Daniel Lidström wrote: > Hello, > > I want to capture the output from valgrind to valgrind_log.txt. > However, the command: > > valgrind --log-file=valgrind_log.txt --num-callers=25 > ./Test/bin/gcc-4.1.1/debug/test >> testing_valgrind.txt > > creates valgrind_log.txt.29297 (as well as testing_valgrind.txt of course). > This effectively makes > it impossible for me to process the output from a script operation, as the > process id changes every time. > Why does valgrind do this? Can I turn off the prefix? > > georog-dev:/home/buildbot/trunk/GFL> valgrind --version > valgrind-3.2.3-Debian > > Thanks in advance! |