Fatal error from Cygwin emacs-w32 every day or so

[Ken Brown]

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