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:mime-version:in-reply-to:references:date
	:message-id:subject:from:to:content-type; q=dns; s=default; b=Ue
	bYzG903TjA+j2/RSHQUjGoR+rSTsFRMnGHamS4Th0KdCZ3nuPF+20JECxuAMlJYf
	gEhIdhjhgiKzmO1vlL+MHKAGxpykNs2Zlt5RbXzMTrz3JlM4PCLC7Wgg0cH52dxU
	7EgnsQV8rhORQ1RuFGU80n0JQpknE6M9X+ohmCvWA=
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:mime-version:in-reply-to:references:date
	:message-id:subject:from:to:content-type; s=default; bh=yVvi7I3x
	u3PCEieVXXoilAUngD8=; b=fkEzRRVnIgw6qRB5UPvYREuNScc7554YgdVcCl6I
	chcfJOGKMtV44klpk1BNNu3Uw1zIJD/D/c4kP7d1dDscgcEe14d8lSqvMqh3dUCC
	F41wqczoIZL6eRc4/etQf63htYZ+oiQL/JcfX0VnKoxjUvL3uh4boAyFCGo/4VEI
	TGI=
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=-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
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)
In-Reply-To: <20140605195104.GA1462@ednor.casa.cgf.cx>
References: <1401832858 DOT 77832 DOT YahooMailNeo AT web185401 DOT mail DOT gq1 DOT yahoo DOT com>	<5390BF87 DOT 6070604 AT cornell DOT edu>	<20140605195104 DOT GA1462 AT ednor DOT casa DOT cgf DOT cx>
Date: Fri, 6 Jun 2014 09:52:55 +0200
Message-ID: <CAEhDDbAxmkDGLTwt5+5nE7bYTQf5qVdu0NswRAZuEMiq=gjyMw@mail.gmail.com>
Subject: Re: Emacs-w32... still crashing
From: Csaba Raduly <rcsaba AT gmail DOT com>
To: cygwin list <cygwin AT cygwin DOT com>
Content-Type: text/plain; charset=ISO-8859-1

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