Mailing-List: contact cygwin-help@sourceware.cygnus.com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe@sources.redhat.com>
List-Archive: <http://sources.redhat.com/ml/cygwin/>
List-Post: <mailto:cygwin@sources.redhat.com>
List-Help: <mailto:cygwin-help@sources.redhat.com>, <http://sources.redhat.com/ml/#faqs>
Sender: cygwin-owner@sources.redhat.com
Delivered-To: mailing list cygwin@sources.redhat.com
Reply-To: <jean.barata@softeam.fr>
From: "Jean Barata" <jean.barata@softeam.fr>
To: "'Cygwin Mailing List'" <Cygwin@Sourceware.Cygnus.Com>
Subject: Re: Bug in pthread ?
Date: Mon, 1 Oct 2001 10:06:03 +0200
Message-ID: <000e01c14a4f$eb2755e0$a5054e0a@sorbonne>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook CWS, Build 9.0.2416 (9.0.2910.0)
X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2314.1300
Importance: Normal


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