[Mingw-notify] [ mingw-Patches-1467551 ] cxa_atexit support in dllcrt

[SourceForge.net <no...@so...>]

Patches item #1467551, was opened at 2006-04-10 19:18
Message generated for change (Comment added) made by dannysmith
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=302435&aid=1467551&group_id=2435

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: None
Group: None
Status: Open
Resolution: None
Priority: 5
Submitted By: Alexander Dubov (oakad)
Assigned to: Nobody/Anonymous (nobody)
Summary: cxa_atexit support in dllcrt

Initial Comment:
When working on some program I'd run into situation  
where g++ insists on cxa_atexit code generation (that  
is, I had to use a specific build of g++). First I  
thought to patch up my code only, but then my program  
would crash before even reaching dllmain. So I  
patched dllcrt1.c and added cxa.c file (borrowed from  
stlport project here on SF, with minor modifications;  
it is essentially identical to all other cxa_atexit  
implementations) to the libmingw32.  
  
I made no modifications to crt1.c as I'm not building  
any executables with my dll's (its a JNI project), so  
I can't test it.  
 
P.S. MSDN says it's ok to initialize mutex objects in 
dllmain. 
 

----------------------------------------------------------------------

>Comment By: Danny Smith (dannysmith)
Date: 2006-04-18 15:12

Message:
Logged In: YES 
user_id=11494

Why is cxa_atexit registration necessay for win32 DLL's?  
Each DLL has its own private atexit table which gets run 
when the DLL unloads?  Couldn't cxa_ateit just be a 
wrapper for dllonexit?

Can you provide a testcase where cxa_atexit is necessary 
or beneficial?

Danny

----------------------------------------------------------------------

Comment By: Danny Smith (dannysmith)
Date: 2006-04-18 15:11

Message:
Logged In: YES 
user_id=11494

Why is cxa_atexit registration necessay for win32 DLL's?  
Each DLL has its own private atexit table which gets run 
when the DLL unloads?  Couldn't cxa_ateit just be a 
wrapper for dllonexit?

Can you provide a testcase where cxa_atexit is necessary 
or beneficial?

Danny

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=302435&aid=1467551&group_id=2435