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=t+o1LbJ16vtkuir0pVRoojRdIWL8Jg4pgFH/cGv3EPe
	xOegx32G2kCbkZCGMP6xFZYFU8kugsF5SeDX8YFzqr8jXrrwyVrK0saMfJtk/8Xy
	+4kRpgbjFSaigbZLI4bKphycJkIHkRFPrkMEUKUuuwRd/NHN1fQ5U8ZnI3a0+lyo
	=
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=Woct8xsMiZfFHN+s15hzDnyy9sA=; b=WMf/G9GAAaUCSCbNE
	y3gM669g2NF1xWa76GNceQbFdaH1Vq4ZcJJxqL6Ocn3q0ySKp31wLsmvoji8ewGJ
	pzuCMkkhU6Q7gA9AnhUDoMdEbtBy0Hq6RwAP/O67CieSPK55rk781abaPQAkbFqP
	iweFn0Z1xGnGnEwZHwlQNJbSxE=
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.7 required=5.0 tests=AWL,BAYES_00,RP_MATCHES_RCVD,SPF_PASS autolearn=ham version=3.3.2
X-HELO:	limerock01.mail.cornell.edu
X-CornellRouted:	This message has been Routed already.
Message-ID:	<534C0A80.2070308@cornell.edu>
Date:	Mon, 14 Apr 2014 09:19:12 -0700
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.4.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> <B8D164BED956C5439875951895CB4B2225C0101D AT WABOTH9MSGUSR8C DOT ITServices DOT sbc DOT com>
In-Reply-To:	<B8D164BED956C5439875951895CB4B2225C0101D@WABOTH9MSGUSR8C.ITServices.sbc.com>
X-IsSubscribed:	yes

On 4/13/2014 6:46 PM, KARR, DAVID wrote:
>> -----Original Message-----
>> Of Ken Brown
>> Sent: Sunday, April 13, 2014 5:43 PM
>> Subject: Re: Fatal error from Cygwin emacs-w32 every day or so
>>
>> On 4/13/2014 10:53 AM, KARR, DAVID wrote:
>>> 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.
>>
>> A gdb backtrace might or might not be helpful.  I would start with other
>> things first (see below).
>>
>>> Is this a known problem?
>>
>> No.
>>
>>> Is there any useful information I could provide?
>>
>> Since this is a new computer, my first suggestion would be to check the
>> BLODA list (http://cygwin.com/faq/faq.html#faq.using.bloda).  If that
>> doesn't help, please make a more detailed report, following the
>> guidelines here:
>>
>>> Problem reports:       http://cygwin.com/problems.html
>
> (Sigh.  It died again while I was writing this note.)
>
> Ok.  I have McAfee on this box.  Note that we've had McAfee installed on all laptops here for quite a while, including my older Win32 box, which I didn't see this problem on.

Are you sure there's nothing else?  Windows Defender maybe?

> I'm attaching the cygcheck.out file. I only elided my laptop hostname.

Nothing jumps out at me in the cygcheck output.

> I followed the instructions for creating a backtrace (running "gdb -p <emacspid>" before clicking YES, and then "continue", and then "bt").  However, it just said "No stack.".

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.

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

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 -