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:from:to:subject:date:message-id:references :in-reply-to:content-type:content-transfer-encoding :mime-version; q=dns; s=default; b=TNHcmd+w1xxPYRz9M2SoBy9oTtp15 CCrvP4pcoJHOIqSaET7zb1cM4m9ioX8+fpx+FYJJQmAIMNf5tiMO+rDIAB/VzQM/ a/g3P34mKk+04e+SJcsuN20NwN9osYYpZumFHIS3N1gmvrtDDJeTkQ2QcLuZc57x fegwS/J95xIda0= 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:from:to:subject:date:message-id:references :in-reply-to:content-type:content-transfer-encoding :mime-version; s=default; bh=kOJW/UE1mKLl0rCQ+jx1eXgiXcU=; b=lQj nzqJ227szkVK5Agk9E64lHwW9YEK6uHVyikRHCW8JzMidb0JxeNSvPtI0WFWIgvR wxKWvKGsTH8TmTWNB24oWvYHvnIt77IBsA4DwBLzYhYpCAjKALEHr0F8zKN7fxf2 H8SxCdqGqDpGdFmpvyEd0XEOIhtjd+fb4wrTS/1A= Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , 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.6 required=5.0 tests=AWL,BAYES_00,RP_MATCHES_RCVD autolearn=ham version=3.3.2 X-HELO: nbfkord-smmo06.seg.att.com X-MXL-Hash: 534c0cc43f935935-e13afe5bea65afd467c54934285736f4b9f85ce8 From: "KARR, DAVID" To: "cygwin AT cygwin DOT com" Subject: RE: Fatal error from Cygwin emacs-w32 every day or so Date: Mon, 14 Apr 2014 16:28:28 +0000 Message-ID: References: <534B2EFE DOT 4010509 AT cornell DOT edu> <534C0A80 DOT 2070308 AT cornell DOT edu> In-Reply-To: <534C0A80.2070308@cornell.edu> Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 X-RSA-Inspected: yes X-RSA-Classifications: public X-AnalysisOut: [v=2.0 cv=W6OPo2qk c=1 sm=1 a=srMsL6ituuWTYeky9Bs9mA==:17 a] X-AnalysisOut: [=94PlVXF_xlIA:10 a=ofMgfj31e3cA:10 a=YnP4VLJI-BoA:10 a=BLc] X-AnalysisOut: [eEmwcHowA:10 a=kj9zAlcOel0A:10 a=zQP7CpKOAAAA:8 a=XIqpo32R] X-AnalysisOut: [AAAA:8 a=w_pzkKWiAAAA:8 a=n2dohBNnwYJ45ZeIT-4A:9 a=CjuIK1q] X-AnalysisOut: [_8ugA:10 a=9c8rtzwoRDUA:10 a=buB1NfXUTBUA:10] X-Spam: [F=0.2000000000; CM=0.500; S=0.200(2010122901)] X-MAIL-FROM: X-IsSubscribed: yes Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by delorie.com id s3EGT7QX022039 > -----Original Message----- > Of Ken Brown > Sent: Monday, April 14, 2014 9:19 AM > Subject: Re: Fatal error from Cygwin emacs-w32 every day or so > > 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 looked through the BLODA list, and I believe that McAfee is the only one that I have installed. > > 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 > " 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 Ok, I'll see if I can do that. > 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. Ok. > One other question: Can you find a way to reproduce the problem, or does > it just seem to happen randomly? In fact, I've never seen it fail while I'm doing something in the Emacs window, it's always when I'm off doing something else. -- 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