X-Recipient: archive-cygwin AT delorie DOT com
DomainKey-Signature: a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:date:from:to:subject:message-id:reply-to
	:references:mime-version:content-type:in-reply-to; q=dns; s=
	default; b=tOiteKvJj7mGutLWxMUDhQlABbhyq5/usIEOVhiNl4jREJK9SLADz
	et+8cxUFICJNjRVmZgWX95LUOGpBiDt6UUkfbOkZPYmK2uVOu3JO7iwHgBDcp4Zd
	T4pbw2jVq00JO3HyKObMbrbDuAxG6zS/gfCHpCuk77UnU2le3TLlvU=
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:date:from:to:subject:message-id:reply-to
	:references:mime-version:content-type:in-reply-to; s=default;
	 bh=ffT4OimZOwpV8HaXRXRBHmpcqvc=; b=q6vzmA686Z3luFwvfVllSveETjfU
	SCaYtzOZ1H5qfYiFoAxXGUGnuAEfxQIveghwCDOAEsAGptzAWk99ZUFYuuP+KYlE
	Cug038i1YJZ9R62c0KPKLM4E1nd6nzkpn1B7ulKfzJnLzmOgY/nu8AsJo61lOy+Y
	BQ8QuSOTHY4vbAs=
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Id: <cygwin.cygwin.com>
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Delivered-To: mailing list cygwin AT cygwin DOT com
Authentication-Results: sourceware.org; auth=none
X-Virus-Found: No
X-Spam-SWARE-Status: No, score=-6.0 required=5.0 tests=AWL,BAYES_00,RCVD_IN_DNSWL_NONE autolearn=ham version=3.3.2
X-HELO: mho-02-ewr.mailhop.org
X-Mail-Handler: Dyn Standard SMTP by Dyn
X-Report-Abuse-To: abuse AT dyndns DOT com (see http://www.dyndns.com/services/sendlabs/outbound_abuse.html for abuse reporting information)
X-MHO-User: U2FsdGVkX19O/ISP121w4Wjg/T/CK0jv
Date: Thu, 5 Jun 2014 15:51:04 -0400
From: Christopher Faylor <cgf-use-the-mailinglist-please AT cygwin DOT com>
To: cygwin AT cygwin DOT com
Subject: Re: Emacs-w32... still crashing
Message-ID: <20140605195104.GA1462@ednor.casa.cgf.cx>
Reply-To: cygwin AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
References: <1401832858 DOT 77832 DOT YahooMailNeo AT web185401 DOT mail DOT gq1 DOT yahoo DOT com> <5390BF87 DOT 6070604 AT cornell DOT edu>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <5390BF87.6070604@cornell.edu>
User-Agent: Mutt/1.5.20 (2009-06-14)

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.  The next snapshot will have that change.

cgf

--
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