valgrind - Find memory leak in a shared library

Question

I need to know ways to find out the memory leaks in a shared library which will be loaded to a release binary. I mean shared library I built with -g option but the binary that l

Answer 1

As the previous answer suggests, this is because you have closed your libraries before the program terminates and therefore symbol information is not available to valgrind.

Using LD_PRELOAD didn't work for me; I now have two builds; one that explicitly does not call dlclose(); on this build, valgrind correctly reports line number information as you would expect with dynamic linking.