Mailing-List:	contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe:	<mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive:	<http://sources.redhat.com/ml/cygwin/>
List-Post:	<mailto:cygwin AT cygwin DOT com>
List-Help:	<mailto:cygwin-help AT cygwin DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender:	cygwin-owner AT cygwin DOT com
Mail-Followup-To:	cygwin AT cygwin DOT com
Delivered-To:	mailing list cygwin AT cygwin DOT com
Message-ID:	<025001c2254b$393c6730$1800a8c0@LAPTOP>
From:	"Robert Collins" <robert DOT collins AT syncretize DOT net>
To:	"Clemens Fuchslocher" <clfuit00 AT fht-esslingen DOT de>, <cygwin AT cygwin DOT com>
References:	<57370207062339390-100000 AT foo>
Subject:	Re: 1.3.12: pthread mutex - second lock won't block.
Date:	Sun, 7 Jul 2002 10:14:12 +1000
MIME-Version:	1.0
X-Priority:	3
X-MSMail-Priority:	Normal
X-MimeOLE:	Produced By Microsoft MimeOLE V6.00.2600.0000

----- Original Message -----
From: "Clemens Fuchslocher" <clfuit00 AT fht-esslingen DOT de>
To: <cygwin AT cygwin DOT com>
Sent: Sunday, July 07, 2002 8:40 AM
Subject: 1.3.12: pthread mutex - second lock won't block.


> hi,
>
> If I lock a fast mutex twice, it normaly should block forever.

Huh? You need to read the pthread spec at least once.

Cygwin's default pthread mutex type is RECURSIVE. And the pthread mutex
attribute calls will reject any 'normal' or 'errorchecking' mutex type
requests. It's fully in the pthread spec is this regard.

If your application is assuming that the default mutex type is non
recursive, it is a bug in your code.

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/

- Raw text -