1.1.3 and upwards: apparent bug with pthread_cond_wait() and/or signal()

[Robert Collins]

> -----Original Message-----
> From: Christopher January [mailto:chris@atomice.net] 
> Sent: Wednesday, May 01, 2002 10:40 PM
> To: cygwin@cygwin.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 <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...... (!)

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/