https://svn.boost.org/trac10/ticket/1323 <p> If test_barrier is run under certain resource constraints then an assertion violation is triggered during cleanup. I believe this assertion error indicates a bug. </p> <p> Note: if Boost.Test is used and a signal got raised in response to hitting a resource limit then the problem could actually be in Boost.Test. </p> <p> Example run with LIMIT_NPROC == 20 (using Linux x86_64, gcc 3.4.6 and also with gcc 4.1.2): </p> <p> Running 1 test case... unknown location(0): fatal error in "test_barrier": std::exception: boost::thread_resource_error </p> <p> <strong>* 1 failure detected in test suite "Master Test Suite" test_barrier_lib: ../libs/thread/src/condition.cpp:354: boost::detail::condition _impl::~condition_impl(): Assertion `res == 0' failed. </strong></p> <p> The first error message is the correct response. The second looks like a bug. </p> en-us /htdocs/site/boost.png https://svn.boost.org/trac10/ticket/1323 Trac 1.4.3 Anthony Williams Mon, 12 Nov 2007 18:05:55 GMT https://svn.boost.org/trac10/ticket/1323#comment:1 https://svn.boost.org/trac10/ticket/1323#comment:1 <ul> <li><strong>status</strong> <span class="trac-field-old">new</span> → <span class="trac-field-new">assigned</span> </li> </ul> <p> The assertion failure implies a bug in the use of barrier (and hence condition). pthread_cond_destroy should only fail if there is still a thread waiting on the condition when it is destroyed, which is an application bug. </p> Ticket Anthony Williams Wed, 14 Nov 2007 16:19:28 GMT https://svn.boost.org/trac10/ticket/1323#comment:2 https://svn.boost.org/trac10/ticket/1323#comment:2 <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">fixed</span> </li> </ul> Ticket