https://bugs.kde.org/show_bug.cgi?id=474443
--- Comment #7 from Paul Floyd <pjfl...@wanadoo.fr> --- Not directly relevant, I work for Siemens EDA and I used to work for Synopsys. So my facetious answer is - use QuestaSim :-) Just some comments on the logs to start with. Lots of the errors refer to obfuscated names used by VCS, so it's hard to tell where the problem is. Something is trying to close files (and failing): ==98899== at 0xC2317A0: __close_nocancel (in /usr/lib64/libpthread-2.17.so) ==98899== by 0x7FBC153: SNPSle_417a3676075ec189542ebd57460c18ac (in /datacenter/tools/synopsys/vcs-mx/O-2018.09-SP2/linux64/lib/libvcsnew.so) Errors like ==98899== Syscall param write(buf) points to unaddressable byte(s) ==98899== Syscall param msync(start) points to uninitialised byte(s) could be harmless. Valgrind can't tell when data structures have holes or padding. Do you get the same result if you use --errors-for-leak-kinds=none? My suspicion is that when you have leak detection on the leak count up to the execve() is getting added to the error count. -- You are receiving this mail because: You are watching all bug changes.
