Problem with threads started in a dynamically loaded bundle under Mac OS X

[Daniel Fenner <dfenner@…>]

The attached program (main.cpp) loads a bundle and calls the function exported herein. The code in the bundle (bundle.cpp) simply starts a thread, joins it and exits. Then the bundle is unloaded. After a few hundred of these cycles program crashes.

To compile and create the bundle one might use the following command lines:

g++ -x c++ -arch i386 -IPATH/TO/BOOST/HEADER  -c bundle.cpp -o bundle.o

mkdir -p bundle.plugin/Contents/MacOS

g++ -o bundle.plugin/Contents/MacOS/bundle -LPATH/TO/BOOST/LIB -lboost_thread-xgcc40-mt-1_37 -arch i386 -bundle bundle.o 

and for the loader:

g++ -x c++ -arch i386 -I/Developer/Headers/FlatCarbon/ -c main.cpp -o main.o

g++ -o main -framework CoreFoundation -arch i386 main.o

I reproduced this behavior with macosx 10.4 / 10.5 and boost 1.35/1.36/1.37/current trunk. My gcc version is 4.0.1.

[viboes]

Could we consider that this is a duplicate of #3926 thread_specific_ptr + dlopen library causes a SIGSEGV, or vice versa?

[viboes]

Moved to Support request until resolution clarified

[viboes]

Duplicate. #3926 thread_specific_ptr + dlopen library causes a SIGSEGV, or vice versa?