Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Delivered-To: mailing list cygwin@cygwin.com Date: Fri, 22 Feb 2002 09:57:02 -0500 From: Jason Tishler Subject: Threaded Cygwin Python Problem (was Re: Creating a local mirror ...) In-reply-to: To: "Gerald S. Williams" Cc: Cygwin Mail-followup-to: "Gerald S. Williams" , Cygwin Message-id: <20020222145702.GD1316@hp.com> MIME-version: 1.0 Content-type: text/plain; charset=us-ascii Content-transfer-encoding: 7BIT Content-disposition: inline User-Agent: Mutt/1.3.24i References: <20020222133107.GB1316@hp.com> Jerry, On Fri, Feb 22, 2002 at 08:48:13AM -0500, Gerald S. Williams wrote: > I would be interested in more information on the pthreads > problem and possibly helping out with the fix, although I > haven't taken the time to dig around in the code and find > the offending code yet. If I followed the thread properly, > there is some dependency on a SignalObjectAndWait function > that isn't natively supported on Windows and hasn't been > emulated correctly, so there is now a race condition. Thanks for your offer to help. See the following for more details: http://cygwin.com/ml/cygwin-developers/2001-10/msg00191.html http://cygwin.com/ml/cygwin-developers/2001-10/msg00193.html > BTW, Cygwin is not the only platform to have problems with > pthreads. Another member of my group found a problem with > the Solaris pthreads package that he had to work around. Please provide more details on the above. Maybe the same or similar workaround could help for Cygwin too? Thanks, Jason -- 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/