https://bugs.kde.org/show_bug.cgi?id=424530
--- Comment #2 from Chris de CLAVERIE <c.de-clave...@pm.me> --- I see. I tried everything in the settings to force the use of the right executable path (I have multiple launch targets, changed them from project target to executable, changed working directories, etc...) but nothing seems to influence the Valgrind plugin. I'm not sure why. I tried looking at the code but having no experience of KDev plugins I had no success. A nice workaround is to use Valgrind "extra parameters" to input the full path to the executable (for example, in meson, "./build/tests/my_unit_test") -- You are receiving this mail because: You are watching all bug changes.
