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=YLp02tcRqk9O0/mw000nRU3JECDdSH8qXaKItr9Lvc2
	Hw+OGBmPstfNbcYTMKzHDQc7KNPGkCElXLaxY6OGLREgJlP9RscsqlOpJ1QjPTnp
	jTJsDD+oydDULVdtD0Vi3PveJXQlo5DsIPGNF17V3TKvY5dUH/vMafNfgDie2iHk
	=
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=C4HuxlxMtVut3f9MP1kUWtSej/o=; b=mlbH1GZpE8hTQavpH
	+GpSNnHVS4RbIUA787nJQSsOdTvCmFJAnHbHwRecsfDN4wdegBPR+tAWLwpI5RSR
	gRFDxwifQJMhtOVwO5wcdOOcCpCUcKphEKgonS8AOQFL0QNY0MpuqCv6tXLaG4QS
	a7RYQm4hqu7AS0Lt4APnfdyq5E=
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
X-Spam-SWARE-Status:	No, score=-3.0 required=5.0 tests=AWL,BAYES_00,KHOP_RCVD_UNTRUST,KHOP_THREADED,RCVD_IN_DNSWL_LOW,RCVD_IN_HOSTKARMA_NO,RP_MATCHES_RCVD,SPF_NEUTRAL autolearn=ham version=3.3.2
Message-ID:	<520B8F34.7000703@cs.utoronto.ca>
Date:	Wed, 14 Aug 2013 10:07:48 -0400
From:	Ryan Johnson <ryan DOT johnson AT cs DOT utoronto DOT ca>
User-Agent:	Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/20130801 Thunderbird/17.0.8
MIME-Version:	1.0
To:	cygwin AT cygwin DOT com
Subject:	Re: 64-bit emacs crashes a lot
References:	<51F3151D DOT 7040000 AT cs DOT utoronto DOT ca> <51F33565 DOT 1090406 AT cornell DOT edu> <51F33F52 DOT 4060405 AT cs DOT utoronto DOT ca> <51FB1D9E DOT 5090102 AT cs DOT utoronto DOT ca> <20130802080211 DOT GA18054 AT calimero DOT vinschen DOT de> <51FB9228 DOT 2020309 AT cornell DOT edu> <51FBA100 DOT 90005 AT cs DOT utoronto DOT ca> <51FD5462 DOT 5020400 AT cs DOT utoronto DOT ca> <51FFBDFF DOT 7040501 AT cornell DOT edu> <51FFC4F2 DOT 8080909 AT cs DOT utoronto DOT ca> <5203D89E DOT 6030801 AT cornell DOT edu> <5203DCCA DOT 1010105 AT cs DOT utoronto DOT ca> <5205B364 DOT 8090007 AT cs DOT utoronto DOT ca> <52064730 DOT 50404 AT cornell DOT edu> <52065B3C DOT 6060104 AT cs DOT utoronto DOT ca> <52067FDD DOT 4000708 AT cornell DOT edu> <520B8E7F DOT 6060709 AT cs DOT utoronto DOT ca>
In-Reply-To:	<520B8E7F.6060709@cs.utoronto.ca>

On 14/08/2013 10:04 AM, Ryan Johnson wrote:
> After a rash of crashes where I either forgot to attach gdb or forgot 
> to set appropriate breakpoints, I finally managed to catch the stack 
> trace below. It occurred during M-x compile, while emacs parsed the 
> compilation's rather copious output, which is by far the most common 
> type of crash I've been getting lately. I have no idea how to 
> interpret the backtrace, though.
False alarm... that backtrace was triggered by me attempting to 
terminate the compile with C-c C-k, which emacs handled fine once gdb 
let it continue.

Ryan


--
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 -