Mumit Khan khan@NanoTech.Wisc.EDU
Fri Feb 4 08:06:00 GMT 2000

On Fri, 4 Feb 2000, M Dipperstein wrote:

> There have been several postings to the list which discuss pthreads and
> the lack of "thread safety" in cygwin.  I was hoping somebody would
> clarify the statement that cygwin is not thread safe.

Cygwin is thread-safe by default as of 2000-01-05 or so snapshot (or
perhaps even a bit earlier). Last year, you had to build it yourself
to get the thread-safe code. It's still being worked on, so there are
bound to be problems, but seems to work ok.

> I'm developing a thread package from the QuickThreads primitives.  The
> final target is not cygwin, but it's a great tool for development along
> the way.  So far, there seem to be no problems using the QuickThreads
> primitives in code compiled with gcc under cygwin.

As long as it's not C++ using exception handling you should be fine. Until
we enhance the Cygwin's pthread interface, the C++ runtime is still single

> Are the only concerns regarding thread safety related to non-reentrant code
> in the cygwin libraries?  If that's the only problem, I think I don't have
> to worry.  The thread package I'll be working with is cooperative, and
> will not allow for library routines to be reentered before they have
> returned.

Try it out and see what happens. We can try and fix the problems, but need
to know what those are first.


Want to unsubscribe from this list?
Send a message to

More information about the Cygwin mailing list