Mailing-List:	contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm
List-Subscribe:	<mailto:cygwin-subscribe AT sources DOT redhat DOT com>
List-Archive:	<http://sources.redhat.com/ml/cygwin/>
List-Post:	<mailto:cygwin AT sources DOT redhat DOT com>
List-Help:	<mailto:cygwin-help AT sources DOT redhat DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender:	cygwin-owner AT sources DOT redhat DOT com
Delivered-To:	mailing list cygwin AT sources DOT redhat DOT com
Reply-To:	<jean DOT barata AT softeam DOT fr>
From:	"Jean Barata" <jean DOT barata AT softeam DOT fr>
To:	"'Cygwin Mailing List'" <Cygwin AT Sourceware DOT Cygnus DOT 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
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/

- Raw text -