https://svn.boost.org/trac10/ticket/13115 <p> I'm using boost::shared_mutex for the reader/writer. My readers have some kinds of dependency which mean Reader A will exit only after Reader B finish. At this situation, exclusive_waiting_blocked will block other readers even when there exists some readers already get the shared_lock, which cause the deadlock. </p> <p> I suppose if there are readers already hold the shared_lock, other readers should be able to gain the shared_lock as well. unique_lock should exclude other readers only when all existing readers are done. Do I make sense? </p> <p> Is this a semantic unclear? Any solution to fix my problem? Is there any reader-biased shared_lock in boost? </p> en-us /htdocs/site/boost.png https://svn.boost.org/trac10/ticket/13115 Trac 1.4.3 viboes Tue, 22 Aug 2017 20:58:31 GMT https://svn.boost.org/trac10/ticket/13115#comment:2 https://svn.boost.org/trac10/ticket/13115#comment:2 <ul> <li><strong>owner</strong> changed from <span class="trac-author">Anthony Williams</span> to <span class="trac-author">viboes</span> </li> <li><strong>status</strong> <span class="trac-field-old">new</span> → <span class="trac-field-new">assigned</span> </li> </ul> Ticket viboes Tue, 22 Aug 2017 22:02:32 GMT https://svn.boost.org/trac10/ticket/13115#comment:3 https://svn.boost.org/trac10/ticket/13115#comment:3 <ul> <li><strong>type</strong> <span class="trac-field-old">Bugs</span> → <span class="trac-field-new">Support Requests</span> </li> </ul> <p> Moved to support request until we have a better understanding of the issue </p> Ticket viboes Thu, 24 Aug 2017 06:25:53 GMT https://svn.boost.org/trac10/ticket/13115#comment:5 https://svn.boost.org/trac10/ticket/13115#comment:5 <ul> <li><strong>status</strong> <span class="trac-field-old">assigned</span> → <span class="trac-field-new">closed</span> </li> <li><strong>resolution</strong> → <span class="trac-field-new">obsolete</span> </li> </ul> <p> Closed as there is no follow up. </p> Ticket