Greg Troxel <[EMAIL PROTECTED]> 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. _______________________________________________ Guile-devel mailing list Guile-devel@gnu.org http://lists.gnu.org/mailman/listinfo/guile-devel
