https://bugs.kde.org/show_bug.cgi?id=458118
--- Comment #4 from Michael Barth ---
I do believe it is a result of the destructor being called and not specifically
delete or free. Using placement new with malloc'd memory and calling the
destructor manually yields the same kind of segment
https://bugs.kde.org/show_bug.cgi?id=458118
--- Comment #2 from Michael Barth ---
(In reply to Paul Floyd from comment #1)
> Does --keep-debuginfo=yes make any difference?
>
> Also can you provide a small example that reproduces the issue?
This does not make any difference for me. H
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
Stat
