Opened 8 years ago

Last modified 8 years ago

#11119 closed Bugs

mutex::lock must not throw — at Initial Version

Reported by: viboes Owned by: Anthony Williams
Milestone: Boost 1.58.0 Component: thread
Version: Boost 1.57.0 Severity: Problem
Keywords: Cc:

Description

The Mutex requirements say

m.unlock();

Requires:

    The current thread owns m. 
Synchronization:

    This operation synchronizes with subsequent lock operations that obtain ownership on the same object. 
Effects:

    Releases a lock on m by the current thread. 
Return type:

    void. 
Throws:

    Nothing. 

However mutex::unlock throws an exception.

Change History (0)

Note: See TracTickets for help on using tickets.