This is the mail archive of the
cygwin@cygwin.com
mailing list for the Cygwin project.
Re: 1.1.3 and upwards: apparent bug with pthread_cond_wait() and/or signal()
- From: "Tim and Kathy Andvaag" <andvaag at sk dot sympatico dot ca>
- To: <cygwin at cygwin dot com>
- Date: Thu, 16 May 2002 23:23:52 -0500
- 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...... (!)
>Please, please release thread-enabled C++ libs.
>Chris
Thanks for this hint.
I rebuilt gcc with
./configure --enable-threads=yes
make
make install
and it solved my intermittent problems with running/compiling the iperf
package (uses threads and C++ libs).
Is there a reason this is not the default?
Tim
P.S. why is:
$ nice -n -1 nice
0
Yet the adjusted priorities are clearly occuring when you look at the
windows task manager?
--
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/