| Summary: | Valgrind additional parameters are not completely kept... | ||
|---|---|---|---|
| Product: | [Applications] kdevelop | Reporter: | Simon MARTIN <simartin> |
| Component: | Plugin: Valgrind integration | Assignee: | kdevelop-bugs-null |
| Status: | RESOLVED FIXED | ||
| Severity: | normal | CC: | gkyla, mattr, moloh |
| Priority: | NOR | ||
| Version: | git master | ||
| Target Milestone: | --- | ||
| Platform: | unspecified | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed In: | ||
| Sentry Crash Report: | |||
| Attachments: |
patch solves problem with repeating --tool=memcheck
patch solves problem with repeating --tool=memcheck |
||
For me, it doesn't keep ANY information. yup, the valgrind config doesn't appear to save any information. kdevelop 3.1.92 (KDE 3.1.92 beta2, CVS 050210) First time I opened Debug -> Valgrind Memory Leak Check, "Additional Parameters" were empty. Afterwards, each time the dialog was opened "--tool=memcheck" was appended: 1. "" 2. "--tool=memcheck" 3. "--tool=memcheck --tool=memcheck" 4. "--tool=memcheck --tool=memcheck --tool=memcheck" (but no more than three times, any changes to "Additional Parameters" are lost) See #90078 as well. This bug still exists in kdevelop 3.2.0 (KDE 3.4.0, Gentoo packages) Yep, for current CVS version, the problems mentioned here persist. Additionally, add #3, I get four and more "--tool=memcheck" on the commandline. :( By the way: changes of the path to the valgrind-binary aren't kept either (kdevelop 3.2.0, KDE 3.4.0). Created attachment 13711 [details]
patch solves problem with repeating --tool=memcheck
patch solves problem with repeating --tool=memcheck
Created attachment 13712 [details]
patch solves problem with repeating --tool=memcheck
patch solves problem with repeating --tool=memcheck in params editbox
*** Bug has been marked as fixed ***. |
Version: 3.0.90-CVS (using KDE 3.2.90 (CVS >= 20040117), compiled sources) Compiler: gcc version 3.2.2 20030222 (Red Hat Linux 3.2.2-5) OS: Linux (i686) release 2.6.3 I start Valgrind ("Tools" -> "Valgrind Memory Leak Check") with the following additional parameters : "--tool=memcheck --leak-check=yes". It works fine, but the next time I try to run Valgrind the "Additional parameters" box only contains "--tool=memcheck"... Since all other boxes are correctly saved, I assume it's a bug.