DomainKey-Signature: a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:message-id:date:from:mime-version:to:subject
	:references:in-reply-to:content-type:content-transfer-encoding;
	 q=dns; s=default; b=y3Clt6kzGQcpgTrCeDje25/sHA2hYP58X0t9vQjA+nt
	VdUb6QPE4yRNjvKdx9AjlqlJPbf1rO5kDqLDaYAkY6U/gw7emX2sOOVkBjwRI47G
	Oeiw8finTXQYbcicx2ZKvAxeGgtIKRk9U30jLNe0Wi6kLP8CuLGCFUbg7b1GPgrA
	=
Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com
Message-ID: <5390CE8F.1080202@cornell.edu>
Date: Thu, 05 Jun 2014 16:09:51 -0400
From: Ken Brown <kbrown@cornell.edu>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.5.0
MIME-Version: 1.0
To: cygwin@cygwin.com
Subject: Re: Emacs-w32... still crashing
References: <1401832858.77832.YahooMailNeo@web185401.mail.gq1.yahoo.com> <5390BF87.6070604@cornell.edu> <20140605195104.GA1462@ednor.casa.cgf.cx>
In-Reply-To: <20140605195104.GA1462@ednor.casa.cgf.cx>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

On 6/5/2014 3: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.  The next snapshot will have that change.

Thanks.  Gustav, can you install the latest snapshot?  That might help 
debug this in case you get that WFSO failure again.

Ken


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