Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com Delivered-To: mailing list cygwin@cygwin.com X-Originating-IP: [203.94.167.76] X-Originating-Email: [arashp@hotmail.com] X-Sender: arashp@hotmail.com From: "Arash Partow" To: cygwin@cygwin.com Subject: Re: Problems with pthread mutexes - update Date: Mon, 27 Sep 2004 07:11:33 +0000 Mime-Version: 1.0 Content-Type: text/plain; format=flowed Message-ID: X-OriginalArrivalTime: 27 Sep 2004 07:12:01.0798 (UTC) FILETIME=[4912FA60:01C4A461] X-IsSubscribed: yes Hi all, This is a follow up to the setting mutex attribute issue, it turns out Brian was correct, by zeroing off the pthread_mutexattr_t with memset all the nastiness seems to go away... The following code which doesn't exhibit the previously mentioned error: int result = 0; pthread_mutexattr_t mutex_attr; memset(&mutex_attr,0,sizeof(mutex_attr)); if ((result = pthread_mutexattr_init(&mutex_attr)) != 0) { printf("Error - Description: %s\n",stderror(result)); exit(EXIT_FAILURE); } Arash Partow __________________________________________________ Be one who knows what they don't know, Instead of being one who knows not what they don't know, Thinking they know everything about all things. http://www.partow.net -- 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/