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
Status: REPORTED
Severity: wishlist
Priority: NOR
Component: memcheck
Assignee: jsew...@acm.org
Reporter: andrew.penneba...@gmail.com
Target Milestone: ---
Some C/C++ developers use the convention of not bothering to free memory at the
point where an application will immediately terminate, either by invoking
exit(), or returning an integer value from the main() CLI entrypoint. This
convention has the benefit of finishing the application a little more quickly,
and also uses less code.
Could leak checks provide an option to ignore this situation? Leaks are mainly
a problem for long-running programs, especially loops, not where program
termination is imminent.
--
You are receiving this mail because:
You are watching all bug changes.
