X-Recipient: archive-cygwin AT delorie DOT com X-Spam-Check-By: sourceware.org Date: Thu, 19 Nov 2009 13:44:05 +0100 From: Corinna Vinschen To: cygwin AT cygwin DOT com Subject: Re: 1.5.25-15: pthread_join deadlocks Message-ID: <20091119124405.GF29173@calimero.vinschen.de> Reply-To: cygwin AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com References: <4B052C11 DOT 6010307 AT ece DOT cmu DOT edu> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <4B052C11.6010307@ece.cmu.edu> User-Agent: Mutt/1.5.20 (2009-06-14) Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm Precedence: bulk List-Id: List-Unsubscribe: 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 On Nov 19 12:29, Ryan Johnson wrote: > Hi all, > > I'm hitting a deadlock with cygwin pthreads when joining on a > short-lived thread -- for me the second such thread creation will > almost never return. It looks *exactly* like a problem that others > noticed as far back as early 2005 [0], and from the output of > strace on the test case (below) the culprit is almost certainly a > racy optimization in __cygwin_lock_* for which a patch was submitted > six months ago [1]. > > As of today my cygwin distribution is completely up to date. Any > hope of an update coming out soon? The update will be Cygwin 1.7. You testcase works fine for me on Cygwin 1.7, so maybe you should try this path. See http://cygwin.com/#beta-test Corinna -- Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Project Co-Leader cygwin AT cygwin DOT com Red Hat -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple