| Summary: | valgrind memcheck does not start with a helloworld. Where is the menu | ||
|---|---|---|---|
| Product: | [Applications] kdevelop | Reporter: | maxime.haselbauer |
| Component: | Plugin: Valgrind integration | Assignee: | kdevelop-bugs-null |
| Status: | RESOLVED WORKSFORME | ||
| Severity: | normal | CC: | anton |
| Priority: | NOR | ||
| Version First Reported In: | unspecified | ||
| Target Milestone: | --- | ||
| Platform: | Other | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed/Implemented In: | ||
| Sentry Crash Report: | |||
|
Description
maxime.haselbauer
2017-08-31 20:52:05 UTC
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. Hello. My valgrind version is 3.11 This is all what I see when launching valgrind memmcheck, or what do you call the "tool view"? /home/max/Projects/Test_projects/testcpp> /usr/bin/valgrind --tool=memcheck --xml=yes --xml-socket=127.0.0.1:42773 --num-callers=12 --max-stackframe=2000000 --error-limit=yes --leak-resolution=high '--show-leak-kinds=&possible' '--leak-check-heuristics=&none' --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=yes --expensive-definedness-checks=no /usr/bin/plasmoidviewer -a . valgrind: Bad option: --show-leak-kinds=&possible valgrind: &possible is an invalid show-leak-kinds set valgrind: Use --help for more information or consult the user manual. Thank you for reporting this issue in KDE software. As it has been a while since this issue was reported, can we please ask you to see if you can reproduce the issue with a recent software version? If you can reproduce the issue, please change the status to "REPORTED" when replying. Thank you! Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone! This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging Thank you for helping us make KDE software even better for everyone! |