Re: [MinGW-dvlpr] mingw runtime problem: atexit in dll's

[<dan...@ya...>]

 --- Earnie Boyd <ear...@ya...> wrote: > Danny Smith wrote:
> > 
> > 
> >  Please comment on this:  I won't submit it to SF patch tracker yet
> > because it will get ignored there.
> > 
> 
> Your alternative won't work because libiberty is GPL, so your first
> solution sounds like your only solution unless you can come up with a PD
> version that'll work.
> 
> Earnie.

Thanks.  Yes I realised the licensing issue with libiberty.  Is it worth
pursuing is the real question.  I stumbled over this when trying to figure
out why TLS indices (indexes?) weren't being cleaned up by libmingw10.dll
(as reported on list by Tamura Kent). I'm no closer to that one and I'm not
sure it is serious -- the cleanup occurs when the thread detaches.  But
having a usable atexit so that dll's can clean things up for themselves
would be useful.  The hack with atexit/_imp__atexit worries me: I've been
caught already with --export-all (dllcrt2,o code symbols were not being
excluded from exports). That has been fixed with patched ld, but I'll
probably get caught again with --auto-import.  Anyway, I'll exercise it for
a little while before I do any thing serious.

Danny 

> 
> _________________________________________________________
> Do You Yahoo!?
> Get your free @yahoo.com address at http://mail.yahoo.com
> 
> 
> _______________________________________________
> MinGW-dvlpr mailing list
> Min...@li...
> https://lists.sourceforge.net/lists/listinfo/mingw-dvlpr 

http://briefcase.yahoo.com.au - Yahoo! Briefcase
- Manage your files online.