https://bugs.kde.org/show_bug.cgi?id=371770
Bug ID: 371770
Summary: Memleak trace back for overwritten or freed memory
pointers
Product: valgrind
Version: unspecified
Platform: Other
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: NOR
Component: memcheck
Assignee: [email protected]
Reporter: [email protected]
Target Milestone: ---
Would it be possible to have an option in valgrind memleak that could track
when allocated memory was actually leaked?
Since all pointers to active allocated memory are tracked by valgrind, when the
pointer to a piece of active allocated memory gets overwritten or freed (the
pointer, not the memory), that is the moment when the memory leak occurs.
So, if valgrind/memleak could at that moment generate an appropriate error
message showing exactly where the pointer got overwritten or freed, that would
speed up fixing the problem tremendously.
I realize this could be very significant overhead, so this enhanced leak
tracking should be selectable via an option flag.
In a test environment, even several hours of run time for a leaky program
followed by a quick fix, would be much better than a couple of days of
programmer data flow analysis and a possibly ineffective fix or new bug.
--
You are receiving this mail because:
You are watching all bug changes.
