https://bugs.kde.org/show_bug.cgi?id=458118
--- Comment #2 from Michael Barth <spirrw...@gmail.com> --- (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. Here is an example repo: https://github.com/Spirrwell/so_unload_delete_demo It is worth noting that when using --leak-check=full, valgrind does pick up on the fact that there's a leak relating to dlclose in this example. But only when these two things are side-by-side in such a small example would I be able to see the relation between the two. While debugging this big old application, I had a giant wall of leaks and I was trying to debug what I THOUGHT was heap corruption, but was simply this shared library unloading issue. So having ANY little extra hint that this kind of problem occurred would be quite useful. -- You are receiving this mail because: You are watching all bug changes.
