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=cieNkpmou6e9KUtuJwYjCBWzqbLMCONqjpjR2tg3JII
	PXTgFWfNyFVE7raBYDAaS5reEZEaq5vdSMOGjHOLCYDyzhd4YdU7PBhNKwSkDwaD
	AqLATrEx1pKkvZgka1kNLj042lG7U6kZ6YPdSCHYFnZ8hbofHRgHn2W6laIXCqQ0
	=
Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com
Message-ID: <5390BF87.6070604@cornell.edu>
Date: Thu, 05 Jun 2014 15:05:43 -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" <cygwin@cygwin.com>
Subject: Re: Emacs-w32... still crashing
References: <1401832858.77832.YahooMailNeo@web185401.mail.gq1.yahoo.com>
In-Reply-To: <1401832858.77832.YahooMailNeo@web185401.mail.gq1.yahoo.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

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?

We're seeing these strange crashes only on 64-bit Cygwin, FWIW.

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