Roland Schwarz wrote:
Markus Schöpflin wrote:
But I could try to figure out whether the tests also fail here at COMSOFT with gcc 4.1.0. If yes, it would be easier to provide you with call stacks and such things.
Ok, so we can give it a try.
Here are the first results from our single processor machine here at COMSOFT. 1. GCC 4.0.3, works but note the infos.
time ../../../bin.v2/libs/thread/test/test_thread.test/gcc-4_0_3_tru64/debug/threading-multi/test_thread --log_level=all Running 3 test cases... Entering test suite "Master Test Suite" Entering test suite "Boost.Threads: thread test suite" Entering test case "test_sleep" test_thread.cpp(39): info: check in_range(xt, 2) passed Leaving test case "test_sleep" Entering test case "test_creation" test_thread.cpp(47): info: check test_value == 999 passed ../../../libs/thread/test/util.inl(136): info: check 'Timed test didn't complete in time, possible deadlock.' passed Leaving test case "test_creation"; testing time: 16666mks Entering test case "test_comparison" test_thread.cpp(27): info: check thrd != *parent passed test_thread.cpp(29): info: check thrd == thrd2 passed ../../../libs/thread/test/util.inl(136): info: check 'Timed test didn't complete in time, possible deadlock.' passed Leaving test case "test_comparison" Leaving test suite "Boost.Threads: thread test suite" Leaving test suite "Master Test Suite"
*** No errors detected real 0m6.954s user 0m0.652s sys 0m0.024s 2. GCC 4.1.0, hangs. schoepf@area51:/vol2/boost/src/boost-RC_1_34_0/libs/thread/test> time ../../../bin.v2/libs/thread/test/test_thread.test/gcc-4_1_0_tru64/debug/threading-multi/test_thread --log_level=all Running 3 test cases... Entering test suite "Master Test Suite" Entering test suite "Boost.Threads: thread test suite" Entering test case "test_sleep" test_thread.cpp(39): info: check in_range(xt, 2) passed Leaving test case "test_sleep" Entering test case "test_creation" <CTRL-C> real 0m53.983s user 0m37.044s sys 0m0.041s Anything else I can do? Markus