Mailing-List: contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT sources DOT redhat DOT com Delivered-To: mailing list cygwin AT sources DOT redhat DOT com Message-ID: <01c201c14a52$a0270510$01000001@lifelesswks> From: "Robert Collins" To: , "'Cygwin Mailing List'" References: <000e01c14a4f$eb2755e0$a5054e0a AT sorbonne> Subject: Re: Bug in pthread ? Date: Mon, 1 Oct 2001 18:25:21 +1000 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.50.4133.2400 X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400 X-OriginalArrivalTime: 01 Oct 2001 08:32:31.0981 (UTC) FILETIME=[9CFF69D0:01C14A53] ----- Original Message ----- From: "Jean Barata" To: "'Cygwin Mailing List'" 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/