Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Subject: RE: 1.1.3 and upwards: apparent bug with pthread_cond_wait() and/or signal() X-MimeOLE: Produced By Microsoft Exchange V6.0.5762.3 Date: Wed, 1 May 2002 22:57:10 +1000 Message-ID: X-MS-Has-Attach: X-MS-TNEF-Correlator: From: "Robert Collins" To: "Christopher January" , Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by delorie.com id g41DEPX24249 > -----Original Message----- > From: Christopher January [mailto:chris AT atomice DOT net] > Sent: Wednesday, May 01, 2002 10:40 PM > To: cygwin AT cygwin DOT com > Subject: Re: 1.1.3 and upwards: apparent bug with > pthread_cond_wait() and/or signal() > > > > 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 now > and again...... (!) But not that test program - the test program was buggy. Rob -- 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/