[valgrind] [Bug 470021] New: ms_print --peak option to extract just the peak memory size

https://bugs.kde.org/show_bug.cgi?id=470021 Bug ID: 470021 Summary: ms_print --peak option to extract just the peak memory size Classification: Developer tools Product: valgrind Version: unspecified Platform: Other

[valgrind] [Bug 75999] Valgrind tool should also include functionality of code coverage. This will help the developer communitiy to use a single tool for memcheck as well as for code coverage.

https://bugs.kde.org/show_bug.cgi?id=75999 Andrew Pennebaker changed: What|Removed |Added CC||andrew.penneba...@gmail.com --- Comment #5

[valgrind] [Bug 400782] New: Option to ignore leaks immediately preceding program termination

https://bugs.kde.org/show_bug.cgi?id=400782 Bug ID: 400782 Summary: Option to ignore leaks immediately preceding program termination Product: valgrind Version: 3.12 SVN Platform: Other OS: Linux

[valgrind] [Bug 400783] New: valgrind complains about a leak in its own code

https://bugs.kde.org/show_bug.cgi?id=400783 Bug ID: 400783 Summary: valgrind complains about a leak in its own code Product: valgrind Version: 3.14 SVN Platform: Other OS: Linux Status: REPORTED Severity:

[valgrind] [Bug 400783] valgrind complains about a leak in its own code

https://bugs.kde.org/show_bug.cgi?id=400783 --- Comment #2 from Andrew Pennebaker --- When I comment out all of my free()'s, valgrind continues to complain "Invalid free()", and also indicates sections in the valgrind code, not my code. -- You are receiving this mail because: Y

[valgrind] [Bug 400782] Option to ignore leaks immediately preceding program termination

https://bugs.kde.org/show_bug.cgi?id=400782 --- Comment #2 from Andrew Pennebaker --- I'm not the best C/C++ programmer, but I am learning about manual memory management, and I have a small example app that I believe should not require manual free(). However, valgrind is reporting that he

[valgrind] [Bug 400807] New: --error-exitcode still sends the wrong value

https://bugs.kde.org/show_bug.cgi?id=400807 Bug ID: 400807 Summary: --error-exitcode still sends the wrong value Product: valgrind Version: 3.12 SVN Platform: Other OS: Linux Status: REPORTED Severity: nor

[valgrind] [Bug 400783] valgrind complains about a leak in its own code

https://bugs.kde.org/show_bug.cgi?id=400783 --- Comment #4 from Andrew Pennebaker --- I do not see this behavior with earlier versions of valgrind such as 3.12. It’s worth pointing out that this fallacious free() warning is happening on Void Linux, compared to no fallacious warnings in Debian

[valgrind] [Bug 400829] New: unhandled instruction bytes in macOS

https://bugs.kde.org/show_bug.cgi?id=400829 Bug ID: 400829 Summary: unhandled instruction bytes in macOS Product: valgrind Version: 3.14 SVN Platform: Other OS: Linux Status: REPORTED Severity: normal

[valgrind] [Bug 377700] New: Valgrind 3.10 and 3.12 aborting on rdkafka applications

https://bugs.kde.org/show_bug.cgi?id=377700 Bug ID: 377700 Summary: Valgrind 3.10 and 3.12 aborting on rdkafka applications Product: valgrind Version: 3.10.0 Platform: Other OS: Linux Status: UNC