On Wed, Jul 27, 2005 at 05:25:38PM -0400, Doug Philips wrote: >On Wednesday, July 27, 2005, at 04:50PM, Jason Tishler indited: > >>> Of course none of this fixes my real problem with why Python is unable >>> to get a lock... >> >>I was able to reproduce your problem. > >Thank you, it is nice to know it wasn't just some anomaly due to my system >being misconfigured. > > >>So far, I found from stracing the following: >> >> 7743 884473 [main] python2.4 3916 __set_errno: int >> semaphore::_trywait():1761 val 11 >> >>Unfortunately, I won't have the time to debug further for a while. And, >>to be honest, I'm lacking the motivation too... > >I _suspect_ that this is related to the PTHREAD mutex change in the 1.5.18 >release. >So perhaps it wasn't benign for Python, but just didn't show up in the Python >self-tests. >At least, that it what I gather from you being able to reproduce the bug.
semaphore::_trywait doesn't have anything to do with pthread mutexes, AFAIK. -- 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/
