https://bugs.kde.org/show_bug.cgi?id=458118
Bug ID: 458118
Summary: Track deletions of objects from unloaded shared
libraries
Product: valgrind
Version: unspecified
Platform: Other
OS: Linux
Status: REPORTED
Severity: wishlist
Priority: NOR
Component: memcheck
Assignee: jsew...@acm.org
Reporter: spirrw...@gmail.com
Target Milestone: ---
I don't know if this is something that is possible. Consider the following, you
create an object in one shared library that is deleted in another. You then
unload the library that did the allocation, and then proceed to delete the
object. If that object is not trivial and has destructors that need to be
called, you will end up with a segmentation fault.
Valgrind will simply report the issue as "is not stack'd, malloc'd or
(recently) free'd." This had lead me to believing I had some kind of heap
corruption bug with an overwrite or underwrite somewhere that was altering the
pointer to point at something that did not exist. But it was a lot simpler than
that, the shared library that created the object was simply unloaded.
If these kinds of bugs could be found by Valgrind, that would be extremely
helpful.
--
You are receiving this mail because:
You are watching all bug changes.
