Bug#508986: valgrind --callgrind-out-file= produce empty file and don't ouput profile data

Package: valgrind Version: 1:3.3.1-3 If I call valgrind with option --tool=callgrind --callgrind-out-file=vlg_callgrind.log, the file stayes empty. W/O the option the file callgrind.out.pid is written correctly. I used the following options: valgrind --tool=callgrind

Bug#508986: valgrind --callgrind-out-file= produce empty file and don't ouput profile data

Package: valgrind Version: 1:3.3.1-3 Severity: normal If I break the applicaton by signal 11 I get the following messages vom valgrind, and the callgrind.out.pid ist empty: ..snip ==10996== Process terminating with default action of signal 11 (SIGSEGV): dumping core ==10996== Access not within