https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98680
--- Comment #2 from ro at CeBiTec dot Uni-Bielefeld.DE <ro at CeBiTec dot
Uni-Bielefeld.DE> ---
I've just ran arrive_and_wait.exe a 1000 times, and (at least so far)
one instance not only didn't complete within the testsuite's 5 minute
timeout, but hang for an hour, so probably deadlocked with this stack
trace:
18570: ./arrive_and_wait.exe
------------ lwp# 1 / thread# 1 ---------------
fe272989 lwp_park (0, 0, 0)
fe26aca7 cond_wait_queue (8062e5c, 8062e44, 0, fe26b22e) + 67
fe26b2ab __cond_wait (8062e5c, 8062e44, feffd938, fe26b2f6) + 8b
fe26b304 cond_wait (8062e5c, 8062e44, 0, fe26b34c) + 24
fe26b361 pthread_cond_wait (8062e5c, 8062e44, c70f6907, 8051bdd, fe432a74,
fe60dc18) + 21
08051c7c ???????? (feffd9f0, feffd9fd, feffda04, 805221a)
08052351 main (feffdb3c, feffda34, 8051a1d) + 1e1 (arrive_and_wait.cc:43)
08051986 _start (1, feffdbb8, 0, feffdbce, feffdbee, feffdc08) + 46
------------ lwp# 2 / thread# 2 ---------------
fe272989 lwp_park (0, 0, 0)
fe26aca7 cond_wait_queue (8062e5c, 8062e44, 0, fe26b22e) + 67
fe26b2ab __cond_wait (8062e5c, 8062e44, fe09ee98, fe26b2f6) + 8b
fe26b304 cond_wait (8062e5c, 8062e44, b803fa4, fe26b34c) + 24
fe26b361 pthread_cond_wait (8062e5c, 8062e44, c70f6907, 8051bdd, fe0c51d8,
1000000) + 21
08051c7c ???????? (feffd9f0, feffd9fd, fe269c02, 8051ee3)
08052034
std::thread::_State_impl<std::thread::_Invoker<std::tuple<main::{lambda()#1}> >
>::_M_run() (8067d28, 0, 0, 8, 200, 7) + 184 (arrive_and_wait.cc:40)
fe516a2d execute_native_thread_routine (8067d28, fe2c3000, fe09efc8, fe272587)
+ 1d (unique_ptr.h:85)
fe2725db _thrp_setup (fe2f0240) + 9b
fe272930 _lwp_start (0, 0, 0, 0, 0, 0)
