The mutex locks may be rather broken in rawhide glibc-2.1.92-5.
Consistently see pthread_mutex_unlock failing, and inspection
shows what appears to be an inconsistent state in the lock
structure.
(gdb) print allocation_lock
$1 = {__m_reserved = 0, __m_count = 0, __m_owner = 0xbf3ffc00, __m_kind =
2,
__m_lock = {__status = -1090766584, __spinlock = 0}}
The fastlock status is 0xBEFC3908 which suggests the fastlock is held
by a different thread to the owner, preventing the owner releasing the
lock. The kind 2 is correct, as this is an error checking mutex.
The application does work reliably under the RedHat glibc-2.1.3-15,
although it is developmental and could be broken.
Regards
Douglas Crosher