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: Sat, 23 Jul 2005 12:18:43 -0400 From: Jason Tishler To: cygwin AT cygwin DOT com Subject: Re: Known issues with Pthreads in 1.5.18? Message-ID: <20050723161842.GA3440@tishler.net> Mail-Followup-To: cygwin AT cygwin DOT com References: <1122038226 DOT 24364 DOT ezmlm AT cygwin DOT com> <4fc195f205072208471d60b4e0 AT mail DOT gmail DOT com> <13028667 DOT 1122052312636 DOT JavaMail DOT dgou AT mac DOT com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <13028667.1122052312636.JavaMail.dgou@mac.com> User-Agent: Mutt/1.4.1i X-IsSubscribed: yes Doug, On Fri, Jul 22, 2005 at 01:11:52PM -0400, Doug Philips wrote: > >> From: "Dave Korn" > >> in particular the line that says > >> > >> "cgf: Change default value for PTHREAD_MUTEX_DEFAULT to > >> PTHREAD_NORMAL." > > Unfortunately that seems to have borked Python 2.4. I found that out > the hard way after returning from a week offline, I just upgraded > everything to 1.5.18 FWIW, the Cygwin Python 2.4 regression test runs under Cygwin 1.5.18 without hanging and passes all tests. > and as a result dequeuing operations stopped blocking and started > getting "temp. unavailable" errors. The above may be solved by rebasing your system with rebaseall. Jason -- PGP/GPG Key: http://www.tishler.net/jason/pubkey.asc or key servers Fingerprint: 7A73 1405 7F2B E669 C19D 8784 1AFD E4CC ECF4 8EF6 -- 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/