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=S+CXW8bkt8TxSZCk2WiSRKW1hwEpHGlS61viB79mwT+
	eDyKrpOUXqKqHv71MnxVVWpg50ZVV77i+coa7c1cfQMxEevLVbiFau0vKmoha/bp
	rY4jhRZh6ds6ZFYIb2vwA9jIwQR0EYmgMQVfPrQsc+Uv2Dxmf0SakwZjrcXNrBbQ
	=
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=LReGQ2YCUkaQmiGUI7qB5a7TeFc=; b=fE4QTrGtgQGOA97TN
	JX6iuGfmEZ4R2DUpaXv9v152XixHGgIfBsYEVTsAhBz4PFtyETqzM9AXN4ZfXQrt
	KUTA84SwqO9sKIgUoc2dJZUvtABmhNT+TC8KZ+CemDaubUrooKeFw20U6B7u0Zhh
	cX/gQgYz4kncTyCKNnCUweX2ew=
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=-1.3 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: <536C1BA9.8090806@cornell.edu>
Date: Thu, 08 May 2014 20:04:57 -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> <536AE1E8 DOT 4090403 AT cornell DOT edu> <B8D164BED956C5439875951895CB4B222663AA04 AT CAFRFD1MSGUSRIA DOT ITServices DOT sbc DOT com>
In-Reply-To: <B8D164BED956C5439875951895CB4B222663AA04@CAFRFD1MSGUSRIA.ITServices.sbc.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-IsSubscribed: yes

On 5/8/2014 12:03 PM, KARR, DAVID wrote:
>> -----Original Message-----
>> 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.
>
> Just so I'm clear, if I use "-Q" that doesn't load anything, so I can't really do much with that.  I can run it, and I can tell you if it ever fails, but it seems unlikely it ever will, because I can't really do anything with it.
>
> So far, I haven't seen the Q instance fail, when my regular instance has failed several times.

This strongly suggests that something in your .emacs is triggering the 
problem.  I think you'll have to do some experimentation to figure out 
what it is.  If you want to send me your .emacs off list, I'll see if I 
spot anything suspicious.

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