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=QQ+2l0y3y5MrPcWU+ZjlzScU9qe+7ZKB5YHLmRO5LIu
	iUv8IGWRRsOOmoY8itkRMyVXkccaNUGcHWXRGaeOAMvU4m27KeHNGDKEkOs0M+X9
	URSBiI5M3DSS7aQ/IpG0cq7g2l5itM6Ox22bry1CtOg2Yh9tFInTKLWSlqZX1lPc
	=
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Message-ID: <51F33565.1090406@cornell.edu>
Date: Fri, 26 Jul 2013 22:50:13 -0400
From: Ken Brown <kbrown AT cornell DOT edu>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/20130620 Thunderbird/17.0.7
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>
In-Reply-To: <51F3151D.7040000@cs.utoronto.ca>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

On 7/26/2013 8:32 PM, Ryan Johnson wrote:
> Hi all,
>
> Running 64-bit cygwin 1.7.22(0.268/5/3), with emacs-nox 24.3-4 inside
> mintty 1.2-beta1-1, I keep getting seg faults and "Fatal error 6: Aborted"
>
> The most recent stackdump was:
>> Stack trace:
>> Frame        Function    Args
>> 0000021F960  0018006F893 (001008C3C40, 400000000FFF0000, 00180127C0D,
>> 00000229900)
>> 00000000006  00180070D5A (00000000000, 00100000000, 000000001DC,
>> 00000000000)
>> 0000021FB40  00180119F08 (006000670D0, 0000022D440, 0000021FC8C,
>> 00600067178)
>> 000000000C1  00180116FBE (0000021FFD0, 00000000000, 00000000000,
>> 0010049F140)
>> 00000000006  0018011748B (00000000000, 00000000000, 00000000000,
>> 00000000006)
>> 00000000006  0018011765C (00000000000, 00000000000, 00000000000,
>> 00000000000)
>> 00000000006  001801130CB (00000000000, 00000000000, 00000000000,
>> 00000000000)
>> End of stack trace
> ... addr2line translates to:
>> /usr/src/debug/cygwin-1.7.22-1/winsup/cygwin/exception.h:65
>> /usr/src/debug/cygwin-1.7.22-1/winsup/cygwin/exceptions.cc:1453
>> /usr/src/debug/cygwin-1.7.22-1/winsup/cygwin/sigproc.cc:678
>> /usr/src/debug/cygwin-1.7.22-1/winsup/cygwin/signal.cc:248
>> /usr/src/debug/cygwin-1.7.22-1/winsup/cygwin/pinfo.h:171
>> /usr/src/debug/cygwin-1.7.22-1/winsup/cygwin/signal.cc:285
>
> It happens at strange times, invariably during I/O of some kind (either
> keyboard input or output from some compilation window); I don't get the
> impression it's fork-related. I don't know how to get a backtrace from
> emacs, given the way any exception or signal always loses the "userland"
> stack (suggestions welcome).
>
> Anyone else seeing this?

This doesn't really answer your question since I don't use emacs-nox, 
but I've been running 64-bit emacs-X11 and finding it very stable.  I 
typically keep it running for several days at a time.

You say you don't know how to get a backtrace from emacs.  I assume 
you've installed emacs-debuginfo and run emacs under gdb.  Are you 
saying you can never get a backtrace after it crashes?

Ken

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