Re: [Boost-users] 1.36 Threads/ASIO causing SEGV when cleaning up thread specific storage

Ok found the solution. It seems that the (initial threads) thread_exit_callback is being called AFTER the TSS's built in heap has been cleaned. Talk about dangling pointers! This can be fixed by declaring a static tss variable in your class :-D cheers, spider. -- View this message in context: http://www.nabble.com/1.36-Threads-ASIO-causing-SEGV-when-cleaning-up-thread... Sent from the Boost - Users mailing list archive at Nabble.com.