From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 9401 invoked by alias); 6 Jun 2014 07:53:01 -0000 Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com Received: (qmail 9268 invoked by uid 89); 6 Jun 2014 07:53:00 -0000 Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=-2.3 required=5.0 tests=AWL,BAYES_00,FREEMAIL_FROM,RCVD_IN_DNSWL_LOW,SPF_PASS autolearn=ham version=3.3.2 X-HELO: mail-wi0-f169.google.com Received: from mail-wi0-f169.google.com (HELO mail-wi0-f169.google.com) (209.85.212.169) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with (AES128-SHA encrypted) ESMTPS; Fri, 06 Jun 2014 07:52:58 +0000 Received: by mail-wi0-f169.google.com with SMTP id ho1so417068wib.0 for ; Fri, 06 Jun 2014 00:52:55 -0700 (PDT) MIME-Version: 1.0 X-Received: by 10.194.71.19 with SMTP id q19mr4175346wju.21.1402041175426; Fri, 06 Jun 2014 00:52:55 -0700 (PDT) Received: by 10.194.173.2 with HTTP; Fri, 6 Jun 2014 00:52:55 -0700 (PDT) In-Reply-To: <20140605195104.GA1462@ednor.casa.cgf.cx> References: <1401832858.77832.YahooMailNeo@web185401.mail.gq1.yahoo.com> <5390BF87.6070604@cornell.edu> <20140605195104.GA1462@ednor.casa.cgf.cx> Date: Fri, 06 Jun 2014 07:53:00 -0000 Message-ID: Subject: Re: Emacs-w32... still crashing From: Csaba Raduly To: cygwin list Content-Type: text/plain; charset=ISO-8859-1 X-SW-Source: 2014-06/txt/msg00102.txt.bz2 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