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:message-id:date:from:mime-version:to:subject
	:references:in-reply-to:content-type:content-transfer-encoding;
	q=dns; s=default; b=Cc0DlIcIPGY0pILDBGJi1e/MAcS5cipJGMUhbgyzANm
	KDyYqRSnEXpm7iS+MTZDxjFvdrA61Lzg9itcICKDPZRDzJ4aqP84mfbdLv5SV9UU
	UIFYlpy/6SZfVmUiT/os9DyYkbW0pIZCJe8C3Ciaflx5WgYjTLfKfztpDdQZoPLI
	=
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:message-id:date:from:mime-version:to:subject
	:references:in-reply-to:content-type:content-transfer-encoding;
	s=default; bh=Bn3vQXMg9clY6eGvKtr6401jzTk=; b=Vpyj4m4BcuNmb0JDg
	JxTSHGtDn1Ds2keMJhq8aAsQ+LM07+zaiI+IrGMUTzyEZXtxZ3ZfGVBCb4GaQHRS
	ZbtlcISC0WIFKvIYTSCFYvXdNeYClyyW1H2D7iQBTNwPNKc22JGuJswV4w1bqP4I
	1idtG1ldPHVmIr6L2CCSfMMZxw=
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.6 required=5.0 tests=BAYES_00,RCVD_IN_DNSWL_NONE,RP_MATCHES_RCVD,SPF_PASS autolearn=ham version=3.3.2
X-HELO:	limerock03.mail.cornell.edu
X-CornellRouted:	This message has been Routed already.
Message-ID:	<53644FCE.4010206@cornell.edu>
Date:	Fri, 02 May 2014 22:09:18 -0400
From:	Ken Brown <kbrown AT cornell DOT 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 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> <B8D164BED956C5439875951895CB4B2225C01C84 AT WABOTH9MSGUSR8C DOT ITServices DOT sbc DOT com> <534CB0AF DOT 2040504 AT cornell DOT edu> <83y4z7jcb3 DOT fsf AT gnu DOT org> <534D5AB8 DOT 6030201 AT cornell DOT edu> <535308D8 DOT 1070200 AT cornell DOT edu> <87fvksekqn DOT fsf AT Rainer DOT invalid> <87wqe4cv4x DOT fsf AT Rainer DOT invalid>
In-Reply-To:	<87wqe4cv4x.fsf@Rainer.invalid>
X-IsSubscribed:	yes

On 5/2/2014 6:50 AM, Achim Gratz wrote:
> Achim Gratz writes:
>> Sorry for the long delay.  I've now ran the two Emacs versions side by
>> side for two days.  The original has crashed twice during that time and
>> the patched version is still running… so I'd call that a fix.  Thanks!
>
> Just as I had sent this mail, the new Emacs also crashed.  The backtrace
> is likely useless due to the missing symbols (I have it still running in
> gdb, though), but it appears to be one of the timer-triggered crashes
> (these sometimes only produce a lisp error and sometimes crash Emacs and
> I don't think these have anything to do with gnutls).  I guess switching
> to the 24.4 pre-release is more productive than continuing with trying
> to patch the 24.3 version.

I agree.  I'll do that soon.

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

- Raw text -