[Boost-bugs] [Boost C++ Libraries] #8288: discrepancy between boost::asio::detail::posix_mutex and boost::asio::detail::win_mutex

Subject: [Boost-bugs] [Boost C++ Libraries] #8288: discrepancy between boost::asio::detail::posix_mutex and boost::asio::detail::win_mutex
From: Boost C++ Libraries (noreply_at_[hidden])
Date: 2013-03-13 02:59:58

#8288: discrepancy between boost::asio::detail::posix_mutex and
boost::asio::detail::win_mutex
----------------------------------------+-----------------------------------
 Reporter:  Spindizzy_Wizard@…          |       Owner:  chris_kohlhoff
     Type:  Feature Requests            |      Status:  new           
Milestone:  To Be Determined            |   Component:  asio          
  Version:  Boost 1.52.0                |    Severity:  Problem       
 Keywords:                              |  
----------------------------------------+-----------------------------------
 The Windows mutex implementation uses CRITICAL_SECTION, which is
 recursive.  That is, if the same thread locks the same mutex twice, it
 will work.

 The Linux mutex implementation via pthreads uses the default mutex
 settings, which are not recursive.  A thread that locks the same mutex
 twice will deadlock.

 I am suggesting that the pthreads implementation should use the recursive
 mutex settings so that you get the same behavior in both Windows and
 Linux.

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