In article <0c9230c6-d206-5332-d89c-e0b93d3de...@gmx.com>,
Kamil Rytarowski <n...@gmx.com> wrote:
>-=-=-=-=-=-
>-=-=-=-=-=-
>
>
>
>On 31.10.2016 21:23, Taylor R Campbell wrote:
>> Date: Mon, 31 Oct 2016 18:29:56 +0100
>> From: Kamil Rytarowski <n...@gmx.com>
>>
>> pthread_mutex_timedlock(3) is broken and it does not work at all for me,
>> not as a standard mutex (like pthread_mutex_lock(3), sufficiently
>> lengthy timeout makes it a good approximation) neither as a timed variant.
>>
>> If the test is expected to fail, you should mark it xfail with a
>> reference to a PR so that it doesn't draw needless attention to
>> itself.
>>
>> The autobuild system is designed to detect and flag unexpected
>> failures; expected ones should be documented in the PR database
>> instead.
>>
>
>You are right, thank you.
>
>The problem is under investigation right now and is "hot".
I have a patch for it:
http://www.netbsd.org/~christos/deadlock.diff
And a standalone program that reproduces it (from the test):
http://www.netbsd.org/~christos/deadlock.c
christos
