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:from:to:subject:references:date:in-reply-to
	:message-id:mime-version:content-type; q=dns; s=default; b=t4Gg1
	izBqmPJheoUcoQNCkw0V52S370Ae13v6xGjl6jFI/m2gEX6YZqGG2AGbS2QDGQnG
	OTnNrNdZRc5iAmfwZtqrPUZewB3cmtej5neqoh+nJR4GeXZHC5kkTIfYBIAJyJYK
	/OYbQlEeGj38PFb193B3VSKJZj7pEGpXsPALNc=
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:from:to:subject:references:date:in-reply-to
	:message-id:mime-version:content-type; s=default; bh=VQhgG+wH1bD
	NDDzX+kp99P92Yxs=; b=J3DiwOj517otoNXs35qutKggjkiG5XrHSl5dJYbk7PO
	akuWBpYnl4beTcY6xcwTI7tzbMpdhiQZL0womrZWl8YqSHV9+Dsg6tgBU8Swk6gl
	rJwxEHQ4t6pYA/TUjgzcvijHPzc8f7c/o4oe7J7Mbjvl0ztc1RT4XwLh1gjG9Jwc
	=
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=-5.3 required=5.0 tests=AWL,BAYES_00,RCVD_IN_BL_SPAMCOP_NET,RCVD_IN_DNSWL_NONE,SPF_PASS autolearn=no version=3.3.2
X-HELO: mail-in-12.arcor-online.net
X-DKIM: Sendmail DKIM Filter v2.8.2 mail-in-14.arcor-online.net EB44D9BE02
From: Achim Gratz <Stromeko AT nexgo DOT de>
To: cygwin AT cygwin DOT com
Subject: Re: Fatal error from Cygwin emacs-w32 every day or so
References: <B8D164BED956C5439875951895CB4B2225C00EA9 AT WABOTH9MSGUSR8C DOT ITServices DOT sbc DOT com>	<534B2EFE DOT 4010509 AT cornell DOT edu>	<B8D164BED956C5439875951895CB4B2225C0101D AT WABOTH9MSGUSR8C DOT ITServices DOT sbc DOT com>	<534C0A80 DOT 2070308 AT cornell DOT edu>
Date: Mon, 14 Apr 2014 19:21:12 +0200
In-Reply-To: <534C0A80.2070308@cornell.edu> (Ken Brown's message of "Mon, 14	Apr 2014 09:19:12 -0700")
Message-ID: <87ppkjrfnb.fsf@Rainer.invalid>
User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/24.4.50 (gnu/linux)
MIME-Version: 1.0
Content-Type: text/plain

Ken Brown writes:
> You might have to run emacs under gdb and put a breakpoint at
> emacs_abort in order to get a useful backtrace.  But I'm not sure it's
> worth putting a lot of effort into debugging emacs-24.3 at this point,
> because emacs-24.4 is already in its pretest phase.  I'm traveling
> right now, but when I return in about a week I'll build the current
> pretest version for you to try.

I see these crashes on a regular basis (the few times I've managed to
attach gdb to this Emacs instance I've not got any useful backtraces
except that it was always crashing in a timer triggered function).

I'm waiting for 24.4 myself to see if this resolves itself.  In the
meantime I'm just running Emacs from a Cygwin32 instance, that never
crashes for me.

> One other question: Can you find a way to reproduce the problem, or
> does it just seem to happen randomly?

If I had a reproducer, you'd have it by now.


Regards,
Achim.
-- 
+<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+

Samples for the Waldorf Blofeld:
http://Synth.Stromeko.net/Downloads.html#BlofeldSamplesExtra

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