Re: [Boost-bugs] [Boost C++ Libraries] #3926: thread_specific_ptr + dlopen library causes a SIGSEGV.

Subject: Re: [Boost-bugs] [Boost C++ Libraries] #3926: thread_specific_ptr + dlopen library causes a SIGSEGV.
From: Boost C++ Libraries (noreply_at_[hidden])
Date: 2014-02-03 16:28:40

#3926: thread_specific_ptr + dlopen library causes a SIGSEGV.
-------------------------------+----------------------
  Reporter:  pluto@…           |      Owner:  viboes
      Type:  Patches           |     Status:  assigned
 Milestone:  To Be Determined  |  Component:  thread
   Version:  Boost 1.42.0      |   Severity:  Problem
Resolution:                    |   Keywords:
-------------------------------+----------------------

Comment (by kai.dietrich@…):

 Hi all,

 I also got bitten by that one. Our application compiles boost statically
 into a shared library (.so/linux). Users are supposed to dl_open/dl_close
 (potentially often). Each open/close cycle leads to a key/handle leak due
 to boost not freeing the handle and not giving any control over the tls
 handles to the user.

 At the moment the tls keys in thread.cpp and once.cpp are internal and not
 accessible from the outside. Would it be possible to give out a way to the
 user. The windows implementation also has some pretty verbose tls cleanup
 code.

 This bug can be a real production showstopper. I'd give it a way higher
 priority.

-- 
Ticket URL: <https://svn.boost.org/trac/boost/ticket/3926#comment:15>
Boost C++ Libraries <http://www.boost.org/>
Boost provides free peer-reviewed portable C++ source libraries.