From: Anthony Williams (anthony_w.geo_at_[hidden])
Date: 2007-11-14 06:08:57
Martin Wille <mw8329_at_[hidden]> writes:
> Anthony Williams wrote:
>> Anthony Williams <anthony_w.geo_at_[hidden]> writes:
>>> In the barrier test, for example, if the test can't launch enough threads, the
>>> already-launched threads will be waiting on the barrier. The test thread will
>>> then abort, destroying the barrier, whilst still having threads waiting. This
>>> is a bug in the test: the existing threads should be interrupted and joined
>>> under such circumstances.
>> Martin, could you check the attached version of test_barrier.cpp in your
>> environment: it should gracefully interrupt all threads on an exception, and
>> thus avoid the assertion failure.
> This seems to work. I tried various settings of RLIMIT_NPOC and I was
> unable to produce the assertion error.
Thanks. I've checked in the fix to test_barrier, and I'll come up with similar
fixes for the other tests too.
-- Anthony Williams Just Software Solutions Ltd - http://www.justsoftwaresolutions.co.uk Registered in England, Company Number 5478976. Registered Office: 15 Carrallack Mews, St Just, Cornwall, TR19 7UL
Boost list run by bdawes at acm.org, gregod at cs.rpi.edu, cpdaniel at pacbell.net, john at johnmaddock.co.uk