Markus Schöpflin <markus.schoepflin@comsoft.de> writes:
The mutex test now compiles and links, but fails on execution:
====== BEGIN OUTPUT ====== Running 6 test cases... Assertion failed: !res, file ../../../boost/thread/pthread/mutex.hpp, line 176 unknown location(0): fatal error in "test_timed_mutex": signal: SIGABRT (application abort requested) test_mutex.cpp(44): last checkpoint
*** 1 failure detected in test suite "Master Test Suite"
EXIT STATUS: 201 ====== END OUTPUT ======
I wonder if this is related to the warning during compilation:
cxx: Warning: ../../../boost/thread/pthread/recursive_mutex.hpp, line 250: non-void function "boost::recursive_timed_mutex::timed_lock(const boost::system_time &)" should return a value (D:noreturnval) return; ----------------------^
I might be totally off track here, but the warning seems genuine.
The warning is genuine (so I've fixed it), but it's not the problem here --- I got the timed_lock #ifdef the wrong way round again, so it was trying to use an unitialized condition variable in timed_mutex. Please try again, and thanks for your continued patience. Anthony -- 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