On Thu, Jun 5, 2014 at 9:51 PM, Christopher Faylor wrote: > On Thu, Jun 05, 2014 at 03:05:43PM -0400, Ken Brown wrote: >>On 6/3/2014 6:00 PM, Zdzislaw Meglicki wrote: >>> And... another crash. I didn't run it under gdb this >>> time and it didn't dump anything either, but I got >>> interesting new message I didn't see before: >>> >>> *** fatal error - WFSO failed waiting for timer thread, Win32 error 0 >> >>This message comes from the function timer_tracker::cancel in timer.cc >>in the Cygwin sources. I'm afraid I have no idea what the timer thread >>is or why WaitForSingleObject might fail waiting for it. >> >>cgf or Corinna (or anyone else), can you shed any light on what might >>cause this? Could it be BLODA, for instance? > > I really don't see how WaitForSingleObject can fail like this but I have > demoted that fatal condition to a warning and added slightly more > debugging output to it. (snip)
That doesn't seem right. If the return code is WAIT_FAILED, api_fatal *should* be called (which presumably calls GetLastError). Other return values like WAIT_ABANDONED or WAIT_TIMEOUT can be let off with a system_printf. Csaba -- GCS a+ e++ d- C++ ULS$ L+$ !E- W++ P+++$ w++$ tv+ b++ DI D++ 5++ The Tao of math: The numbers you can count are not the real numbers. Life is complex, with real and imaginary parts. "Ok, it boots. Which means it must be bug-free and perfect. " -- Linus Torvalds "People disagree with me. I just ignore them." -- Linus Torvalds -- 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
