Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com Date: Wed, 8 Jun 2005 16:42:28 +0200 From: Corinna Vinschen To: "Cygwin List'" Subject: Re: pthreads, cygwin and pthread_mutex_lock not blocking Message-ID: <20050608144228.GA11065@calimero.vinschen.de> Reply-To: cygwin AT cygwin DOT com Mail-Followup-To: Cygwin List' References: <44f83c19cc33e4382680fe3758164ccf AT rehley DOT net> <20050527202823 DOT GB4939 AT trixie DOT casa DOT cgf DOT cx> <0833be552ca5aa00a72ecef822250580 AT rehley DOT net> <20050528161515 DOT GA1323 AT trixie DOT casa DOT cgf DOT cx> <1064750c32ec165a486fe7dba0f8b302 AT rehley DOT net> <429CA3E8 DOT 7070909 AT acm DOT org> <0483fbf499cd644361f2e16f2e88f7d5 AT rehley DOT net> <4fd08104e6065d20682122c1ee564453 AT rehley DOT net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.4.2i On Jun 7 10:22, Peter Rehley wrote: > Any comments about this? > > On Jun 2, 2005, at 11:22 AM, Peter Rehley wrote: > > >Here is a patch to thread.cc that allows _lock to process signals. > >The patch is against the 1.178 version of thread.cc found in cvs. Thanks for the patch, but it's big enough to require a copyright assignment, unfortunately. See http://cygwin.com/contrib.html. Since cgf hasn't had a look into your patch so far, he's not tainted and will come up with a self-written patch to fix this problem for now. However, if you would be interested to contribute to the Cygwin DLL, I'd be glad to receive your copyright assignment at one point. Corinna -- Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Project Co-Leader mailto:cygwin AT cygwin DOT com Red Hat, Inc. -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/