>This is a bug in your code. You are unlocking an already unlocked mutex. >Cygwin should return EPERM to that call - and I note you are note >checking any error codes from the system calls, which is quite dangerou >programming style.
yes, you're right, I don't need to unlock an already unlocked mutex. and I should have tested the returned values. mea culpa. but, is it a reason to get the program blocked when trying to lock the mutex ? Thanks. -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Bug reporting: http://cygwin.com/bugs.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
