Bug in pthread ?

Robert Collins robert.collins@itdomain.com.au
Mon Oct 1 01:24:00 GMT 2001


----- Original Message -----
From: "Jean Barata" <jean.barata@softeam.fr>
To: "'Cygwin Mailing List'" <Cygwin@Sourceware.Cygnus.Com>
Sent: Monday, October 01, 2001 6:06 PM
Subject: Re: Bug in pthread ?


>
> >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
> ?

No, and I will be looking into this, but as a low priority - for correct
use it hasn't been a problem.

Rob


--
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/



More information about the Cygwin mailing list