id,summary,reporter,owner,description,type,status,milestone,component,version,severity,resolution,keywords,cc 4736,MinGW: tss crashes (SIGSEGV) in ~thread_specific_ptr,Jim Bell ,Anthony Williams,"tss crashes with a SIGSEGV in the destructor of thread_specific_ptr under mingw, inside boost::detail::set_tss_data(). After main() exits, apparently cleanup_tls_key() gets called some time prior to the thread_specific_ptr clean-up. Then inside set_tss_data(), get_or_make_current_thread_data() returns 0, and dereferencing it (current_thread_data->tss_data, line 589) causes the crash. get_or_make_... actually makes one, but get_current_thread_data() won't return it because current_thread_tls_key is reset. So there's a little resource leak here, too. Though I don't think that's important this late in the program's termination sequence, you could check current_thread_tls_key explicitly in get_or_make_... and avoid it. ",Bugs,closed,Boost 1.45.0,thread,Boost 1.44.0,Showstopper,fixed,mingw tss SIGSEGV thread_specific_ptr destructor set_tss_data,jim@… Bryce Adelstein Lelbach