https://bugs.kde.org/show_bug.cgi?id=424530
--- Comment #1 from Milian Wolff <[email protected]> --- The >''< seems to be the issue - it doesn't use the binary of your executable properly - can you check why? this is actually a value that comes from the project builder, so potentially it is a fault in meson after all? The valgrind command itself looks fine. If you replace the >''< with e.g. >'ls'< it will "work": /usr/bin/valgrind --tool=memcheck --xml=yes --xml-socket=127.0.0.1:46421 --num-callers=12 --max-stackframe=2000000 --error-limit=yes --leak-resolution=high --show-leak-kinds=definite,possible --leak-check-heuristics=all --keep-stacktraces=alloc-and-free --freelist-vol=20000000 --freelist-big-blocks=1000000 --undef-value-errors=yes --show-mismatched-frees=yes --partial-loads-ok=yes --track-origins=no --expensive-definedness-checks=no 'ls' -a . ==19563== Failed to connect to XML logging server '127.0.0.1:46421'. ==19563== XML output will be sent to stderr instead. -- You are receiving this mail because: You are watching all bug changes.
