Re: [Boost-bugs] [Boost C++ Libraries] #8306: named mutex does not unlock as expected

Subject: Re: [Boost-bugs] [Boost C++ Libraries] #8306: named mutex does not unlock as expected
From: Boost C++ Libraries (noreply_at_[hidden])
Date: 2013-03-18 18:58:10

#8306: named mutex does not unlock as expected
--------------------------------------------------------+-------------------
  Reporter:  David Hebbeker <david.hebbeker@…>          |       Owner:  igaztanaga                                                        
      Type:  Bugs                                       |      Status:  new                                                               
 Milestone:  To Be Determined                           |   Component:  interprocess                                                      
   Version:  Boost 1.52.0                               |    Severity:  Optimization                                                      
Resolution:                                             |    Keywords:  named mutex, named_mutex, semaphore, posix_named_semaphore, unlock
--------------------------------------------------------+-------------------

Comment (by David Hebbeker <david.hebbeker@…>):

 Replying to [comment:1 steven_watanabe]:
 > Violating the preconditions of a function has undefined behavior.  Once
 you do this, you cannot rely on the object (or the program) being in a
 sane state.
 Yes, I am acknowledging that this scenario would violate the preconditions
 defined in the documentation. My intention is that the behaviour is not as
 one would expect it from a mutex in general (see [Tanenbaum]).

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