Mailing-List:	contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm
List-Subscribe:	<mailto:cygwin-subscribe AT sourceware DOT cygnus DOT com>
List-Archive:	<http://sourceware.cygnus.com/ml/cygwin/>
List-Post:	<mailto:cygwin AT sourceware DOT cygnus DOT com>
List-Help:	<mailto:cygwin-help AT sourceware DOT cygnus DOT com>, <http://sourceware.cygnus.com/ml/#faqs>
Sender:	cygwin-owner AT sourceware DOT cygnus DOT com
Delivered-To:	mailing list cygwin AT sourceware DOT cygnus DOT com
Date:	Fri, 4 Feb 2000 06:32:25 -0800 (PST)
From:	M Dipperstein <mdipper AT cs DOT ucsb DOT edu>
X-Sender:	mdipper AT dinah
To:	cygwin AT sourceware DOT cygnus DOT com
Subject:	Threads
Message-ID:	<Pine.GSO.4.05.10002040619080.4230-100000@dinah>
MIME-Version:	1.0

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.

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.

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.

-Mike


--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe AT sourceware DOT cygnus DOT com

- Raw text -