https://bugs.kde.org/show_bug.cgi?id=384247
--- Comment #1 from Anton Anikin <anton.ani...@htower.ru> --- Hi. First, check version of your valgrind installation. Valgrind from ubuntu/neon 16.04 is ok, but some other versions can be buggy, see for example https://bugreports.qt.io/browse/QTCREATORBUG-18473 If you use "normal" valgrind, please paste full run cmd (first line) from "Test" tool view, something like /usr/bin/valgrind --tool=memcheck --xml-socket=127.0.0.1:37349 --xml=yes --num-callers=12 .... On my neon 16.04 I can't reproduce your bug. > Can't figure out where I should change the valgrind launch command "Run" menu -> "Configure Launches..." -> select "Valgrind" subitem for your launch configuration -> change valgrind run settings. -- You are receiving this mail because: You are watching all bug changes.
