Subject: [boost] [thread]Forever sleeping
From: Niklas Angare (li51ckf02_at_[hidden])
Date: 2017-02-22 22:39:33
Recent runs of my regression test runner NA-QNX660-x86 leave a lot of
Boost.Thread test executables stuck in nanosleep, waiting for a condition
variable, or both.
Commit 544eda  which switched from CLOCK_REALTIME to CLOCK_MONOTONIC
seems suspicious to me. If the returned timespec is ever compared to values
based on the CLOCK_REALTIME epoch, such as system_clock, the results will be
quite undesirable. Are you sure the return values of timespec_now() are only
ever compared to each other and values based on the CLOCK_MONOTONIC epoch?
Boost list run by bdawes at acm.org, gregod at cs.rpi.edu, cpdaniel at pacbell.net, john at johnmaddock.co.uk