* Dave Brolley wrote on Wed, Jan 24, 2007 at 11:14:56PM CET: > >> > >> I have trouble reproducing this bug easily. Which system does it happen > >> on? > > It happened in a cygwin 1.6.9 environment on Windows XP Home edition.
Confirmed on Cygwin. > >> In what order > >> are things opened/linked against, which ones are closed explicitly, for > >> this to trigger? Do you mix calls to lt_dlopen with direct calls to > >> dlopen? Do you mix libraries created with libtool with libraries > >> created without? > > These questions will take some time to sort out. No need for answers any more, thanks. > Given time, I should be able to come up with a test case if necessary. I have a test. Will post and apply both when I have it cleaned up. > You are correct. I have attached a new patch which corrects this and > also corrects a problem with my previous patch. My previous patch causes > an infinite loop in the case that a resident library is in the linked > list. Ah, good to know. I should test for that as well. Thanks again, Ralf > 2007-01-24 Dave Brolley <[EMAIL PROTECTED]> > > * libltdl/ltdl.c (lt_dlexit): Make sure that 'cur' is not NULL before > checking that it is still in the list. > _______________________________________________ Bug-libtool mailing list Bug-libtool@gnu.org http://lists.gnu.org/mailman/listinfo/bug-libtool
