Boost C++ Libraries: Ticket #3269: boost thread - mutex.lock() doesn't throw exception

component changed; owner set

talanchor@… — Thu, 16 Jul 2009 13:30:18 GMT

owner set to Anthony Williams
component None → thread

Steven Watanabe — Fri, 21 Aug 2009 14:09:45 GMT

What errors do you expect from pthread_mutex_lock?

anonymous — Mon, 31 Aug 2009 12:50:11 GMT

What errors do you expect from pthread_mutex_lock?

mutex.lock() call may fail - and it sometimes does (according, for example, to POSIX mutexes), so we need to know that something went wrong. One way to report an error is to throw system_error exception, like for example just::thread library does: http://www.stdthread.co.uk/doc/headers/mutex/mutex/lock.html

Steven Watanabe — Mon, 31 Aug 2009 15:22:01 GMT

Well, it doesn't fail randomly. Most of the possible failures either cannot happen with boost::mutex or are a result of undefined behavior. However, EAGAIN and ENOMEM appear to be possible.

anonymous — Fri, 04 Sep 2009 14:07:54 GMT

Replying to steven_watanabe:

Well, it doesn't fail randomly. Most of the possible failures either cannot happen with boost::mutex or are a result of undefined behavior. However, EAGAIN and ENOMEM appear to be possible.

On QNX pthread_mutex_lock may also return EDEADLK - if mutex was not set as recursive, or ETIMEDOUT if "A kernel timeout unblocked the call", and all this return values including EAGAIN are possible. At least this errors should be logged somewhere and execution of the thread should be cancelled.

Steven Watanabe — Fri, 04 Sep 2009 14:44:09 GMT

Relocking a mutex that is already locked by the current thread is undefined behavior, so EDEADLK is irrelevant.

version, milestone changed

anonymous — Tue, 13 Oct 2009 13:20:39 GMT

version Boost 1.39.0 → Boost 1.40.0
milestone Boost 1.40.0 → Boost 1.41.0

version, milestone changed

anonymous — Tue, 09 Mar 2010 13:15:25 GMT

version Boost 1.40.0 → Boost 1.43.0
milestone Boost 1.41.0 → Boost 1.43.0

viboes — Fri, 21 May 2010 15:34:21 GMT

I propose to resolve as invalid as works as designed.

status changed; resolution set

Anthony Williams — Fri, 21 May 2010 17:14:25 GMT

status new → closed
resolution → fixed

Fixed on trunk