On Sat, Dec 30, 2006 at 11:51:18AM +0100, Christian Biere wrote:
> The problem is not this function itself but how it's used. I'm no
> threadpert but I could think of a hack that is
> 
> 		pthread_mutex_trylock(mutex));
> 		pthread_mutex_unlock(mutex);

This just hides the bug - you could set PTHREAD_DIAGASSERT to A instead.

If you can not figure out how this particular mutex is supposed to be
locked/unlocked, it is probably best to just report this upstream - the
maintainers will probably know how to fix it (and the fix is typically
very easy).

Martin