Re: [Boost-bugs] [Boost C++ Libraries] #2219: conditional_variable_any::any fails to release recursive_mutex when mutex has been acquired by the same thread more than one time

Subject: Re: [Boost-bugs] [Boost C++ Libraries] #2219: conditional_variable_any::any fails to release recursive_mutex when mutex has been acquired by the same thread more than one time
From: Boost C++ Libraries (noreply_at_[hidden])
Date: 2008-09-02 10:08:02

#2219: conditional_variable_any::any fails to release recursive_mutex when mutex
has been acquired by the same thread more than one time
--------------------------------------+-------------------------------------
  Reporter:  brad_wade_at_[hidden]  |       Owner:  anthonyw                              
      Type:  Bugs                     |      Status:  closed                                
 Milestone:  Boost 1.36.0             |   Component:  thread                                
   Version:  Boost 1.36.0             |    Severity:  Regression                            
Resolution:  wontfix                  |    Keywords:  condition_variable_any recursive_mutex
--------------------------------------+-------------------------------------
Changes (by anthonyw):

  * status:  new => closed
  * resolution:  => wontfix

Comment:

 This works as designed. condition_variably_any::wait() calls unlock on the
 supplied mutex. For a recursive mutex this only does one level of
 unlocking.

 Completely unlocking a recursive mutex is not safe in the general case. I
 did not realise that the old boost::condition supported it. This facility
 has never been tested in the boost::condition tests. I will add it to the
 list of breaking changes.

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