pthread_join() broken on Cygwin 1.5.11-1?

I just upgraded my Cygwin installation to the new 1.5.11-1 release, and now one of my applications behaves strangely. The application in question is multi-threaded. Everything seems to be working fine until the application tries to exit. The application consists of the main thread and several s

Re: CYGWIN 1.5.9-1 - Is vprintf() not thread safe?

How about posting a simple test case. If you do so, I'll try and take a look. -- Brian Ford Senior Realtime Software Engineer VITAL - Visual Simulation Systems FlightSafety International the best safety device in any aircraft is a well-trained pilot... #include #include pthread_mutex_t printf_m

Re: CYGWIN 1.5.9-1 - Is vprintf() not thread safe?

From: Brian Ford <[EMAIL PROTECTED]> To: John William <[EMAIL PROTECTED]> Subject: Re: CYGWIN 1.5.9-1 - Is vprintf() not thread safe? On Sun, 16 May 2004, John William wrote: > I'm having problems with a program that uses vprintf() to show error > messages. The program w

CYGWIN 1.5.9-1 - Is vprintf() not thread safe?

I'm having problems with a program that uses vprintf() to show error messages. The program works fine when run as a single-threaded program. When compiled as a multi-threaded program, the console output of vprintf() is "interleaved" with output from the various threads mixed together. With a la

Readdir() bug?

I have a program that behaves differently on Linux and Cygwin. I'm using version 1.3.9 of the DLL. The program tries to list all files in a directory by doing opendir(), then readdir() until all the entries have been read and then closedir(). That works fine, but the time between the opendir()