Re: Known issues with Pthreads in 1.5.18?

2005-07-22 Thread Doug Philips
>> From: "Dave Korn" <[EMAIL PROTECTED]> >> To: >> Date: Fri, 22 Jul 2005 11:47:40 +0100 >> Subject: RE: Known issues with Pthreads in 1.5.18? >> The default type of mutex just got changed, from error checking, to >> normal. If your code is setting up a default mutex and then one thread >> atte

Re: rebaseall failure?

2005-07-27 Thread Doug Philips
On Wednesday, July 27, 2005, at 12:45PM, Jason Tishler <[EMAIL PROTECTED]> indited: >> ReBaseImage (/usr/bin/cygiconv-2.dll) failed with last error = 6 > >The above implies that /usr/bin/cygiconv-2.dll was in use when you >executed rebaseall. If rebaseall is run from ash, then the above should >

Re: rebaseall failure?

2005-07-27 Thread Doug Philips
On Wednesday, July 27, 2005, at 02:29PM, Christopher Faylor <[EMAIL PROTECTED]> indited: >It looks like a "ps -W" might be more instructive. OK (Here it is. Also note that I noticed sh in the list and did a ps -W from the ash immediately after running the script (that output is also enclosed b

Re: rebaseall failure?

2005-07-27 Thread Doug Philips
On Wednesday, July 27, 2005, at 03:05PM, Jason Tishler <[EMAIL PROTECTED]> indited: >If sh.exe is really bash.exe, then this is why cygiconv-2.dll is in use. >The question is why is sh.exe running in the first place? Indeed. And why does putting that dll at the end of the list make any differenc

Python 2.4.1 locking bug. (was: Re: rebaseall failure?)

2005-07-27 Thread Doug Philips
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.

Re: rebaseall failure?

2005-07-27 Thread Doug Philips
On Wednesday, July 27, 2005, at 04:50PM, Jason Tishler indited: >> My next line of inquiry resulted in putting a 'sleep' in just before >> the rebase invocation. Huh, that fixed it. Weird. > >The sleep gave the sh.exe process time to exit. You "fixed" it but in >an open-loop way that is still pro

Python 2.4.1 locking bug test case simplified!

2005-07-29 Thread Doug Philips
$ python tbq.py each test group is testing 1000 items sem_init: Resource temporarily unavailable Exception in thread Thread-4: Traceback (most recent call last): File "/tmp/python.572/usr/lib/python2.4/threading.py", line 442, in __bootstrap self.run() File "/tmp/python.572/usr/lib/python2.