This is the mail archive of the
cygwin
mailing list for the Cygwin project.
Re: pthreads, cygwin and pthread_mutex_lock not blocking
- From: Christopher Faylor <cgf-no-personal-reply-please at cygwin dot com>
- To: cygwin at cygwin dot com
- Date: Fri, 27 May 2005 16:28:23 -0400
- Subject: Re: pthreads, cygwin and pthread_mutex_lock not blocking
- References: <44f83c19cc33e4382680fe3758164ccf@rehley.net>
- Reply-to: cygwin at cygwin dot com
On Fri, May 27, 2005 at 10:57:34AM -0700, Peter Rehley wrote:
>I'm trying to use pthread in cygwin, and I'm expecting the function
>pthread_mutex_lock to block when used. However it is returning error
>45 (EDEADLK). I'm using a static initializer for the thread so the
>mutex is type PTHREAD_MUTEX_DEFAULT.
>When I look through the pthread code I see that PTHREAD_MUTEX_DEFAULT
>is set to PTHREAD_MUTEX_ERRORCHECK,
>When I do the same on linux or soloris, the pthread_mutex_lock blocks,
>and looking in the pthread.h file on those systems see that the
>default is set to PTHREAD_MUTEX_NORMAL.
>
>Why is cygwin using PTHREAD_MUTEX_ERRORCHECK as the default? And what
>problems might occur if PTHREAD_MUTEX_DEFAULT is set to
>PTHREAD_MUTEX_NORMAL?
Why not just try it and report the results?
cgf
--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Problem reports: http://cygwin.com/problems.html
Documentation: http://cygwin.com/docs.html
FAQ: http://cygwin.com/faq/