https://bugs.kde.org/show_bug.cgi?id=458118
Philippe Waroquiers <philippe.waroqui...@skynet.be> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |philippe.waroquiers@skynet.
| |be
--- Comment #3 from Philippe Waroquiers <philippe.waroqui...@skynet.be> ---
Valgrind keeps recently freed blocks in a list that allows to report where it
was allocated. If the size of this list (controlled by --freelist-vol
parameter) is big enough and you use --keep-debuginfo=yes, then I think
valgrind should be able to tell you the stack trace that allocated the
referenced freed block.
Now, if the segmentation violation happens because the destructor code has been
unloaded and this destructor code is not found anymore via a pointer in the
dispatch table, then valgrind does not track executable code and/or dispatch
table.
--
You are receiving this mail because:
You are watching all bug changes.
