Boost logo

Boost :

Subject: Re: [boost] [thread]Forever sleeping
From: Vicente J. Botet Escriba (vicente.botet_at_[hidden])
Date: 2017-02-24 14:23:47

Le 24/02/2017 à 13:46, Vicente J. Botet Escriba a écrit :
> 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 [1] 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?
>> [1]
> I'll rollback it and analyze more deeply the change.

Please, let me know if it works again.


Boost list run by bdawes at, gregod at, cpdaniel at, john at