callgrind.out.xxx is empty
Status: Beta
Brought to you by:
weidendo
Menu
▾
▴
#7 callgrind.out.xxx is empty
Using valgrind 2.2.0 and callgrind 0.9.9 or 0.9.10, I
have one user executable that does not dump any data on
exit.
If I force a dump with callgrind -d, I have a
callgrind.out.xxx.1 file that is not empty.
Otherwise the callgrind.out.xxx file is empty.
The executable of my user is a 44Mbytes dynamically
linked using libpthreads
strace seems to say that nothing is written to the file:
12842
open("/0/orion/ctornier/work/cvswork/VSIP/source/apps/GENERIC_APPLICATION/callgrind.out.12842",
O_WRONLY|O_TRUNC) = 0
12842 getpid() = 12842
12842 close(0) = 0
12842 unlink("/tmp/callgrind.info.12842") = 0
It is the first time I see this problem. I was not able
to reproduce it on a small example.
Thanks in advance.
Logged In: YES
user_id=621915
This should be fixed in 0.9.12. Can you confirm?
When opening the dump file returned file descriptor 0,
no output was done. This happens if the applications
closes all file descriptors at end.