Re: Hang in threads.test

[Neil Jerram]

Andy Wingo <address@hidden> writes:

>>> Neil Jerram <address@hidden> writes:
>>>
>>>> My nightly build of master, on a relatively slow old machine, is
>>>> hanging, on most nights, in `make check'.
>>
>> The hang seems to be caused by one thread (A) running (gc) at the same
>> time as another thread (B) is doing GC_malloc_atomic.  The third thread
>> in the backtrace is the signal delivery thread, and not involved.
>>
>> But in the "mutex with owner not retained (bug #27450)" test there is no
>> thread B, so where does it come from?  It's left over from the "locking
>> mutex on behalf of other thread" test, two tests previously.  Adding
>> (join-thread t) to that earlier test means that the thread has to run
>> and complete before we get to the (gc) test.
>
> Is this fixed now for you?

No.  But that might be because the libgc on that machine - Debian
1:7.1-3 - is too old.  What is the latest recommendation for libgc
version?  README says "at least version 7.0", but I suspect that's out
of date.

       Neil