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
From:	Christopher January <chris AT atomice DOT net>
To:	cygwin AT cygwin DOT com
Subject:	Re: 1.1.3 and upwards: apparent bug with pthread_cond_wait() and/or signal()
Date:	Wed, 1 May 2002 13:39:52 +0100
References:	<FC169E059D1A0442A04C40F86D9BA7600C5F6D AT itdomain003 DOT itdomain DOT net DOT au>
In-Reply-To:	<FC169E059D1A0442A04C40F86D9BA7600C5F6D@itdomain003.itdomain.net.au>
MIME-Version:	1.0
Message-Id:	<200205011339.52642.chris@atomice.net>
X-MIME-Autoconverted:	from quoted-printable to 8bit by delorie.com id g41CfHU20850

> Between 1.1.3 and 1.3.0 a huge change occurred in the pthreads code
> base, so this assumption is not safe. (It's not necessarily wrong
> either.) I'd definitely be using 1.3.10 though.
>
> > #include <pthread.h>
> > #include <iostream>
>
> The cygwin c++ libgcc, stdlibc++ and gcc are not built with thread
> support, so C++ and threads may not work well together. C should work
> fine, and if anyone convinces Chris to release a thread-enabled gcc, C++
> should get better.
Arrrgh - so that explains why so much of my source crashes randomly every now 
and again...... (!)
Please, please release thread-enabled C++ libs.

Chris


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