On Wed, 10 Dec 2003, Michael Robbert wrote: > Antoine Labour wrote: > > Actually, I still do believe it's the same problem. In some other mails > > I specified it happens also on single CPU machines. I think other people > > have been able to reproduce it as well. The fact I expose it in a loop > > is because the hang is random. It also sometimes happen in a non-loop > > environment. I suspect a nasty race condition which depends heavily on > > the system scheduling, so in your case the same problem might happen > > every time. > > In any case, I tried my small test case with zsh too, same result : hang > > after a few iterations. > > > Antoine, > I'm sorry, you're probably correct. > > Everybody, > Some new information I got today. I found another user on our campus > that is having the problem on two different machines, but not a third. > All of them running Windows XP. So far every machine I have seen it on > is running XP and is a recent new install of Cygwin. Does anybody think > that they could get closer to a solution if I were to provide you with a > machine to play with remotely where the problem happens every time? > Why not try to debug it your self?
Have you tried to strace it? Can you get a stack trace of the hang in gdb? Note: You may need a debug version of the cygwin1.dll or shell for this to be valid. I will provide the former if you are willing to test it. > Also, Is this the only place for bug reporting for Cygwin? I can't find > any actual bug database like bugzilla to get this officially reported. > Yes. A bugzilla style database has been proposed, but we have not found anyone willing to maintain it yet. Want to volunteer? -- Brian Ford Senior Realtime Software Engineer VITAL - Visual Simulation Systems FlightSafety International Phone: 314-551-8460 Fax: 314-551-8444 -- 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/
