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=nEL3Hz+IHBtpm5P403Adz+itQWQGhoeMnzMOo26S45G
	SsMz7u1+4WWo9obBZ9xiDG7LI84AemKlDxwipZ+Ju0b3ShHgcX1AFOrxPN/dZTY9
	uPbSzC75Lhqkr1mnZk//mukULfmaTv+HiJVBpfvHVFeRCKXqSkv3xhz81DGmO93w
	=
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=JkdCV4bp54k8RP58ClWwWy2RX4U=; b=p06JpwevD6UDqFHTj
	IZyRj5MEkB0GyLXkVRPGAPRp3sPzgu7NK9BmzVrzCy+qMD63BHQw2LbIqNdluMJr
	P0kLoWbEGB68a7N44krgnyFSKhSMGSxjI1094sLVvM7705pFHct3MMPVPrZOJ/v3
	oNbSUqlNAt9P2Smi06brRFCTLU=
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,RP_MATCHES_RCVD,SPF_HELO_PASS,SPF_PASS autolearn=ham version=3.3.2
X-HELO:	limerock04.mail.cornell.edu
X-CornellRouted:	This message has been Routed already.
Message-ID:	<54411F5B.5040906@cornell.edu>
Date:	Fri, 17 Oct 2014 09:53:31 -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> <54406ED0 DOT 9060502 AT cornell DOT edu>
In-Reply-To:	<54406ED0.9060502@cornell.edu>
X-IsSubscribed:	yes

On 10/16/2014 9:20 PM, Ken Brown wrote:
> 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.

If this turns out not to be the issue, then I think you would need an 
unoptimized build for further debugging.  I can provide one for you.

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 -