From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 5570 invoked by alias); 1 May 2002 12:39:57 -0000 Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com Received: (qmail 5536 invoked from network); 1 May 2002 12:39:55 -0000 Received: from unknown (HELO duck.doc.ic.ac.uk) (146.169.1.46) by sources.redhat.com with SMTP; 1 May 2002 12:39:55 -0000 Received: from voxel25.doc.ic.ac.uk ([146.169.49.175] helo=voxel25 ident=ccj00) by duck.doc.ic.ac.uk with esmtp (Exim 3.16 #7) id 172tOk-00006G-00 for cygwin@cygwin.com; Wed, 01 May 2002 13:39:54 +0100 Content-Type: text/plain; charset="iso-8859-1" From: Christopher January To: cygwin@cygwin.com Subject: Re: 1.1.3 and upwards: apparent bug with pthread_cond_wait() and/or signal() Date: Wed, 01 May 2002 05:39:00 -0000 References: In-Reply-To: MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable Message-Id: <200205011339.52642.chris@atomice.net> X-SW-Source: 2002-05/txt/msg00017.txt.bz2 > 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 > > #include > > 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 n= ow=20 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/