id,summary,reporter,owner,description,type,status,milestone,component,version,severity,resolution,keywords,cc
3926,thread_specific_ptr + dlopen library causes a SIGSEGV.,pluto@…,viboes,"hi,

i've discovered that using thread_specific_ptr in shared library dlopened from thread causes a gpf.[[BR]]
please consider following scenario:
[[BR]][[BR]]
spawn thread[[BR]]
dlopen a shared library with thread_specific_ptr[[BR]]
dlclose the library[[BR]]
terminate the thread[[BR]]
[[BR]]
observe the gpf[[BR]]
[[BR]]
{{{
Program received signal SIGSEGV, Segmentation fault.
0x00007ffff62b7400 in ?? ()
(gdb) bt
#0  0x00007ffff62b7400 in ?? ()
#1  0x00007ffff7221f79 in __nptl_deallocate_tsd () at pthread_create.c:154
#2  0x00007ffff722291b in start_thread (arg=<value optimized out>) at pthread_create.c:304
#3  0x00007ffff6f9293d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:112
#4  0x0000000000000000 in ?? ()
}}}
afaics the pthread (user provided) destructor keyed to pthread specific data is called on dlunloaded code.[[BR]][[BR]]
BR,[[BR]]
Pawel.


",Bugs,reopened,,thread,Boost 1.42.0,Problem,,,