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=LTNBtgjo5yTJomscV0Kr14PZY8PZEBpB1tYUeWGxG6Q
	FhCYpX26aeFNzhjkgIolO1aKD1mAHgfSmYi7fsz4KfykRBm15SgCjU8nZ9wXd3k6
	0bMNCCytYhHOiJWdPn7W0THnpGSzfztk0p9u15BV/LFefkbQ1OWQzzQ/anTgs3vo
	=
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=nGN/AsDiAyiQgfsBmjrt0Mub6lM=; b=Nz0i19saQPIHw5Ndi
	82z1gjV2yxxoivYzAqCYWNHdAO87Uf1TsgAboTqbPygGorFWZSyLAbh4E2i9be1j
	jHyOso+42dTEDrIKK8K4KY3XvxfmVPdIkozVoP81uGPeP2JqnQxJp6e50sZdaSh2
	oOq0Rmzp12ER2Dun7Shj1PAqSY=
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=-1.2 required=5.0 tests=AWL,BAYES_05,KHOP_RCVD_UNTRUST,KHOP_THREADED,RCVD_IN_DNSWL_LOW,RCVD_IN_HOSTKARMA_NO,RDNS_NONE,SPF_NEUTRAL autolearn=no version=3.3.1
Message-ID: <51F33F52.4060405@cs.utoronto.ca>
Date: Fri, 26 Jul 2013 23:32:34 -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/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> <51F33565 DOT 1090406 AT cornell DOT edu>
In-Reply-To: <51F33565.1090406@cornell.edu>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

On 26/07/2013 10:50 PM, Ken Brown wrote:
> 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"

>> 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?
I do have the emacs-debuginfo. I meant that the stack dump didn't have 
any emacs frames in it (they were all cygwin1.dll), and my experience 
with cygwin/gdb is that once you've taken a signal or exception you lose 
the cygwin stack and just see a bunch of threads mucking around in 
various low-level Windows dlls.

I have tried attaching gdb to emacs and setting a breakpoint on abort(), 
but it didn't catch anything yet. I'm also hampered by gdb constantly 
getting confused, breaking partway into emacs, and having to 
detach/reattach it. I've started a new thread for that issue.

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