Re: memleak in lt_dlexit()

[Norbert Sendetzky]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On Sunday 11 April 2004 20:08, Bob Friesenhahn wrote:
> 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.

Thanks for the hint. It helped me finding the line rather quickly.

Problem:
try_dlopen() uses LT_DLMEM_REASSIGN (line 3099 in 1.5.4), which 
renders LT_DLFREE at the end of the function useless. Problem occurs 
if filename of the library is "libname" instead of "/path/libname".


Norbert

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.6 (GNU/Linux)
Comment: For info see http://www.gnupg.org

iEYEARECAAYFAkB6mDsACgkQxMLs5v5/7eC+WwCeNgaxY1AFFPlPzxLItoVBFfso
RbkAnR0p29Nps2UUZMpXXzOovhOy7cro
=RAO6
-----END PGP SIGNATURE-----

lt_dlexit_trydlopen_memleak.diff
Description: Text Data