https://bugs.kde.org/show_bug.cgi?id=424530

            Bug ID: 424530
           Summary: kdev-valgrind uses the wrong syntax
           Product: kdevelop
           Version: git master
          Platform: Other
                OS: Linux
            Status: REPORTED
          Severity: major
          Priority: NOR
         Component: Plugin: Valgrind integration
          Assignee: kdevelop-bugs-n...@kde.org
          Reporter: c.de-clave...@pm.me
  Target Milestone: ---

This is my first bug report on this platform. Feel free to let me know how to
improve it.

SUMMARY
https://github.com/KDE/kdev-valgrind has been unmaintained for 8 months
according to the Github page. I tried it on my Meson project, and it failed to
run Valgrind.


STEPS TO REPRODUCE
1. Open a Meson project. I didn't try any other project type, but I suspect the
bug would show up with any project
2. Configure Valgrind settings in Run > Configure Launches menu
3. Run your executable using the Run > Run Valgrind Analysis > Run Memcheck
menu 

OBSERVED RESULT
It tries to run the following command :

    /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 '' -a .

This throws a simple "valgrind: : command not found" error, because I suspect
the Valgrind syntax used by the plugin is outdated.

EXPECTED RESULT
Valgrind runs and its output is displayed in the appropriate panel

SOFTWARE/OS VERSIONS
KDE Plasma Version: 5.18.5
KDE Frameworks Version: 5.68.0
Qt Version: 5.12.8

ADDITIONAL INFORMATION
It is interesting to note the plugin is not packaged in ubuntu repositories and
the installation instructions are lacking

-- 
You are receiving this mail because:
You are watching all bug changes.

Reply via email to