https://bugs.kde.org/show_bug.cgi?id=388017
--- Comment #4 from Josef Weidendorfer <josef.weidendor...@gmx.de> --- Good to see that `--trace-children=yes` worked! Just as remark: Callgrind opens a file descriptor at start to allow output to be written to the directory which was the current working directory at prgoram start. The motivation was that a program could change to arbitrary directories during run, and it may be difficult for an user to find the callgrind output. Now if an application wildly closes all kind of file descriptors before termination, it also may close this descriptor and leave callgrind without writing output (this could be detected...). However, you always can ask callgrind to dump output during the program run using callgrind_control. -- You are receiving this mail because: You are watching all bug changes.
