Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/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
From: "Dave Korn" <dk AT artimi DOT com>
To: <cygwin AT cygwin DOT com>
Subject: RE: child thread termination causes main thread error termination
Date: Mon, 11 Oct 2004 14:51:08 +0100
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
In-Reply-To: <7e48807e0485.7e04857e4880@tampabay.rr.com>
Message-ID: <NUTMEGy3JQTQATlpTt20000038c@NUTMEG.CAM.ARTIMI.COM>
X-OriginalArrivalTime: 11 Oct 2004 13:51:08.0392 (UTC) FILETIME=[5C23BE80:01C4AF99]

> -----Original Message-----
> From: cygwin-owner On Behalf Of gmiller
> Sent: 09 October 2004 19:49

> I have a sample thread application that runs under Ferdora 
> Core 2 latest but exits on an error condition under cygwin.  
> If I add sleeps to the end of the child threads then the 
> program will go to completion.  While using "insight" the 
> error can be tracked into the library code.  I have attached 
> the source code and output of cygcheck.  Is this a know 
> problem and if so is there any other workaround.



pthread_cond_t start_cv = PTHREAD_COND_INITIALIZER;
pthread_mutex_t start_mutex = PTHREAD_MUTEX_INITIALIZER;

pthread_cond_t done_cv = PTHREAD_COND_INITIALIZER;
pthread_mutex_t done_mutex = PTHREAD_MUTEX_INITIALIZER;

pthread_mutex_t print_mutex = PTHREAD_MUTEX_INITIALIZER;


  Haven't even tried to run your testcase yet, but I've found static
initialisation of pthread_ types to be unreliable under cygwin; use the
pthread_XXX_init functions instead, and see if that helps.

    cheers, 
      DaveK
-- 
Can't think of a witty .sigline today....


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