https://bugs.kde.org/show_bug.cgi?id=356457
--- Comment #5 from Philippe Waroquiers <philippe.waroqui...@skynet.be> --- (In reply to Joost VandeVondele from comment #3) > just happened again, but it is really rare. (this is a 12 core server > running valgrind +-12h a day... and this seems to happen every +- 10 days). > Is any of the suggestions mentioned above possible without runtime overhead > and excessive IO ? Assuming you know which executable/test causes the bug, the first thing to try is the 'self-hosting', and run your test executable under valgrind self-hosted under itself. and/or run in a loop valgrind on the executable that gave the problem, with the options -v -v -v -d -d -d --vgdb-stop-at=valgrindabexit A failing run will then stop, and allow to examine the debug output of valgrind. The above will for sure consume CPU, but you can sleep during that time :) -- You are receiving this mail because: You are watching all bug changes.
