Subject: Re: [boost] [thread]Forever sleeping
From: Vicente J. Botet Escriba (vicente.botet_at_[hidden])
Date: 2017-02-24 12:46:37
Le 22/02/2017 à 23:39, Niklas Angare via Boost a écrit :
> 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?
I'll rollback it and analyze more deeply the change.
I believed that this was the cause of some timming issues.
Thanks for reporting,
Boost list run by bdawes at acm.org, gregod at cs.rpi.edu, cpdaniel at pacbell.net, john at johnmaddock.co.uk