[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: thread assert with 1.8.2
From: |
Kevin Ryde |
Subject: |
Re: thread assert with 1.8.2 |
Date: |
Thu, 16 Aug 2007 10:35:01 +1000 |
User-agent: |
Gnus/5.110007 (No Gnus v0.7) Emacs/22.1 (gnu/linux) |
Greg Troxel <address@hidden> writes:
>
> Running threads.test
> guile: Error detected by libpthread: Unlocking unlocked mutex.
> Detected by file
> "/usr/home/gdt/NetBSD-current/src/lib/libpthread/pthread_mutex.c", line 357,
> function "pthread_mutex_unlock".
Sounds bad.
> Perhaps someone could try this on Linux with the right magic debug
> variables to object to unlocking an unlocked mutex.
For a gnu system pthread_mutex_unlock returns non-zero for a problem,
except it only notices problems if you use the "error checking" flavour
of mutexes (currently SCM_I_PTHREAD_MUTEX_INITIALIZER is the default
"fast" kind, which don't check).
I suppose a debug-build option to use the checking flavour and look at
the returns would be a good thing. I guess the "fat_mutex" stuff at the
scheme level is supposed to take care of keeping scheme code out of
trouble though.
- Re: thread assert with 1.8.2,
Kevin Ryde <=