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=oJ+r3o6gOaNvzlyltuuYhW5qB7ayHvupPCgkqvO0Vwf
	w5itK/LNT+3BIN1Gi+41kM1PXecIe1FPBbIG5eOcBl3jVGqaLfQPy0WSmMTswFoB
	KKufE5Hk2LQDGV7JDbWK8XR+ksy018NqZTlh9DQqUxdWANIJzeUTXt5s89dJ2Rsg
	=
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=XTqRdl9lCRqBsVeulXkbxIuWfpE=; b=QstkzAnTLl3gGzfn2
	jDxzsXQN8YBGKS9dw0547dVbaW/piuMpxF0WfvQR7t/dJ7N9y0PRL4iEuQOVlD/9
	LFUg+fGtFrTf35ccUDeYm1TEt57vsFQbZjRe3A6I00BSd0WiQJmCFeqoF3qoOcCt
	JgfFFv1N0pNMYtCUa/yjgj4N8I=
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=-0.7 required=5.0 tests=AWL,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: <536AE1E8.4090403@cornell.edu>
Date: Wed, 07 May 2014 21:46:16 -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> <B8D164BED956C5439875951895CB4B2226630D4A AT CAFRFD1MSGUSRIG DOT ITServices DOT sbc DOT com> <B8D164BED956C5439875951895CB4B222663A4D5 AT CAFRFD1MSGUSRIA DOT ITServices DOT sbc DOT com>
In-Reply-To: <B8D164BED956C5439875951895CB4B222663A4D5@CAFRFD1MSGUSRIA.ITServices.sbc.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-IsSubscribed: yes

On 5/7/2014 7:42 PM, KARR, DAVID wrote:
>> -----Original Message-----
>> Of KARR, DAVID
>> Sent: Monday, May 05, 2014 2:34 PM
>>
>>> -----Original Message-----
>>> Of KARR, DAVID
>>> Sent: Sunday, April 13, 2014 10:53 AM
>>>
>>> I recently installed 1.7.29 on a new Win7/64 laptop.  Every day or so, I
>>> get a "fatal error" dialog from emacs-w32.  It asks me if I want to
>> debug
>>> it, but I'm not sure what info I could pull from gdb that would be
>> useful.
>>>
>>> Is this a known problem?
>>>
>>> Is there any useful information I could provide?
>>
>> I installed the test 24.3.90.1 version, and it hasn't crashed once (yet).
>
> Since I reported this, I've seen it crash several times now, but it doesn't give the usual "Debug?" dialog, it just goes away.  It's died several times today.  I'll start running it from gdb to get a stacktrace.

As before, it would be good to know if it crashes when started with the 
-Q option.

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