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
	=
Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com
Message-ID: <520B8F34.7000703@cs.utoronto.ca>
Date: Wed, 14 Aug 2013 10:07:48 -0400
From: Ryan Johnson <ryan.johnson@cs.utoronto.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@cygwin.com
Subject: Re: 64-bit emacs crashes a lot
References: <51F3151D.7040000@cs.utoronto.ca> <51F33565.1090406@cornell.edu> <51F33F52.4060405@cs.utoronto.ca> <51FB1D9E.5090102@cs.utoronto.ca> <20130802080211.GA18054@calimero.vinschen.de> <51FB9228.2020309@cornell.edu> <51FBA100.90005@cs.utoronto.ca> <51FD5462.5020400@cs.utoronto.ca> <51FFBDFF.7040501@cornell.edu> <51FFC4F2.8080909@cs.utoronto.ca> <5203D89E.6030801@cornell.edu> <5203DCCA.1010105@cs.utoronto.ca> <5205B364.8090007@cs.utoronto.ca> <52064730.50404@cornell.edu> <52065B3C.6060104@cs.utoronto.ca> <52067FDD.4000708@cornell.edu> <520B8E7F.6060709@cs.utoronto.ca>
In-Reply-To: <520B8E7F.6060709@cs.utoronto.ca>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit

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