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-19 01:33:32

#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:5 steven_watanabe]:
> Replying to [comment:4 David Hebbeker <david.hebbeker@…>]:
> > What about {{{PTHREAD_MUTEX_ERRORCHECK}}}? In that case an {{{EPERM}}}
 error would be returned, which is better than undefined behaviour.
> But note that it's still considered an error. It's just detected.
> It's not going to happen. The bottom line is that you have to know
 whether you hold a mutex in order to do anything useful with it. I don't
 think that the library should go out of its way to support usage which is
 very dangerous and which is not supported by any other mutex
 implementation that I'm aware of.
 As I understand the behaviour I described is implemented by pthread
 mutexes of type {{{PTHREAD_MUTEX_ERRORCHECK}}}. It improves the behaviour
 as it may not result in an undefined state in contrast to the default
 mutex, but it returns an error value. The downside would be the
 performance overhead.

Ticket URL: <>
Boost C++ Libraries <>
Boost provides free peer-reviewed portable C++ source libraries.

This archive was generated by hypermail 2.1.7 : 2017-02-16 18:50:12 UTC