Re: memleak in lt_dlexit()

[Bob Friesenhahn]

I have not encountered libltdl-related memory leaks in my own
software, but it does not use the features you describe.  I strongly
recommend use of Valgrind (http://valgrind.kde.org/) under Linux to
test for memory leaks and initialization problems.

Bob

On Sun, 11 Apr 2004, Norbert Sendetzky wrote:

> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> Hi all
>
> I've found that user_search_path is not freed if libltdl is finally
> shut down. This results in a memory leak if you call lt_dlinit(),
> lt_dlsetsearchpath("test") and lt_dlexit() in a loop.
>
> There seems to be another one in lt_dlopenext() or in one of its
> called functions, but I haven't found the line yet. It would be nice,
> if someone else would also check for memleaks. Maybe there are more
> around.
>
> Furthermore in try_dlopen() (line 3232 and below in 1.5.4)
> sizeof("string")-1 is used in strncmp(). It seems that this should be
> LT_STRLEN("string") instead, because sizeof(char*)-1 is always 3.
> Thus, the "library_names=" case will never be matched because the
> "libdir=" is used instead.
>
> Thanks
>
>
> Norbert
>
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.0.6 (GNU/Linux)
> Comment: For info see http://www.gnupg.org
>
> iEYEARECAAYFAkB5gZQACgkQxMLs5v5/7eAqUQCeNqB5oL92lsoCNGKSGW3uyz1R
> h4cAoKjvygmMXD8XBiLQ1UdYM/L20vEA
> =JonC
> -----END PGP SIGNATURE-----
>

======================================
Bob Friesenhahn
address@hidden
http://www.simplesystems.org/users/bfriesen