Le 04/04/2012 00:04, Bob Friesenhahn a écrit : > On Tue, 3 Apr 2012, Brice Goglin wrote: >>> It is common for glibc to secretly allocate some memory for its own >>> use, and this is particularly true for multi-threaded programs. Often >>> it has no way to safely release this memory. >> >> I tried with another dependency (libpci instead of libpthread), the >> leaks go away, so indeed the problem is likely outside of libltdl. > > The important thing to test for is that if you load and unload this > module 1000 times, do you see 1000X as much "leak" or the same amount > as when loading/unloading one time?
As I said in my first mail, the amount of leaks doesn't seem to depend on the number of loads/unloads. So it's not annoying, except the valgrind warning, which can be suppressed anyway. thanks Brice _______________________________________________ https://lists.gnu.org/mailman/listinfo/libtool
