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=lnn/RZgKvsDaFo5p8jysrKWfoxXtdFJ1S6dZQlShBgA
	cbcJzjoHnrTNt9bh1IZMqBnJQ2W7ueBRf3yH4ltsYV6dSy6bqoEhMUgos1C72HqO
	9ABmu+2bChSIzbNrt2TQz/Bwf417T0i2S8BD3qrkth3LEnydyT9SDBOVIrtBhZrg
	=
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=MTqi6ZSNPnQTpvivrvIJ/DP40/o=; b=HjgQCZR/yCQWPE2HN
	LzkqWSqS26VlGCt0cyMdmMZDv8O/+F1w6qk5bVMKQZAG06QpBHomsw9xWBGRHSIF
	T0gwvehptYKSaCvQCMNcxxf2hQI0nc1z4KRgFokiYFkcZ1raImOQggVgB/n8/wil
	4savk/pLEkjiPsx8KrZHnPaaqo=
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=-1.8 required=5.0 tests=AWL,BAYES_00,SPF_HELO_PASS,SPF_PASS,T_RP_MATCHES_RCVD autolearn=ham version=3.3.2
X-HELO:	limerock03.mail.cornell.edu
X-CornellRouted:	This message has been Routed already.
Message-ID:	<54406ED0.9060502@cornell.edu>
Date:	Thu, 16 Oct 2014 21:20:16 -0400
From:	Ken Brown <kbrown AT cornell DOT edu>
User-Agent:	Mozilla/5.0 (Windows NT 6.1; WOW64; rv:31.0) Gecko/20100101 Thunderbird/31.2.0
MIME-Version:	1.0
To:	cygwin AT cygwin DOT com
Subject:	Re: [ANNOUNCEMENT] Updated: emacs-24.3.93-3 [TEST]
References:	<announce DOT 54146F07 DOT 1000103 AT cornell DOT edu> <54402903 DOT 1060906 AT dronecode DOT org DOT uk>
In-Reply-To:	<54402903.1060906@dronecode.org.uk>
X-IsSubscribed:	yes

On 10/16/2014 4:22 PM, Jon TURNEY wrote:
> I have been suffering from some crashes with emacs-X11 24.3.93-3 on x86_64
>
> This seems to have crossed my threshold of apathy, so I've been running
> emacs under gdb with a breakpoint on emacs_abort (since it seems to die
> with SIGABORT which can't be usefully backtraced...)
>
> I get a backtrace starting as follows (full backtrace is attached):
[...]

The first thing that strikes me is the Lisp backtrace, which is almost 
300 lines long and keeps repeating the same calls:

"redisplay_internal (C function)" (0x93baf8)
"redisplay" (0x8100b8)
"sit-for" (0x8102f0)
"minimap-update" (0x810668)
"apply" (0x810660)
"byte-code" (0x8107d0)
"timer-event-handler" (0x810b78)
"input-pending-p" (0x810e68)
"sit-for" (0x8110a0)
"minimap-update" (0x811418)
[...]
"input-pending-p" (0x8391b8)
"sit-for" (0x8393f0)
"minimap-update" (0x839768)
"apply" (0x839760)
"byte-code" (0x8398d0)
"timer-event-handler" (0x839c78)

Is it possible that minimap-update has gone into an infinite recursion? 
  Or is this kind of lisp backtrace normal for you (e.g., if you stop 
emacs and examine the backtrace at random times)?  I'm afraid I don't 
know anything about minimap, but the first thing I'd do is try to figure 
out what's going on with minimap-update.

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 -