Hi,<br><br>I am using boost::thread for a plug-in that is loaded by a third-party Linux application. I have no control over the host&#39;s threading or when it chooses to unload my code.<br><br>Unfortunately I experience a crash every time the host thread unloads the .so and terminates. I get the following backtrace:<br>
<br>(gdb) bt<br>#0  0x00007fffde12c460 in ?? ()<br>#1  0x00000032cf607889 in start_thread () from /lib64/libpthread.so.0<br>#2  0x00000032cf2e5ccd in clone () from /lib64/libc.so.6<br><br>Not much to go on...<br><br>I am pretty confident the crash is happening in a pthread key destructor registered by Boost. The only parts of the boost::thread library I am currently using are the synchronization classes:<br>
<br>shared_mutex,<br>shared_lock,<br>unique_lock,<br>upgrade_lock,<br>upgrade_to_unique_lock<br><br>I&#39;m not directly using any thread-specific storage myself.<br><br>What I would like to do is force boost to call its TSS destructor in my plug-in&#39;s destroy_dso() function. Is this at all possible?<br>
<br>Many thanks,<br><br clear="all">- Andrew<br>