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=wl6fhnDKAic184mU/ujk/v9A5NERyPj8CxwwHb95j0e
	3AO+2sZNKjVJArfkEK6NUgbo5Q8xnaBaYUMfLGUCFuUh6VxC6OoldH8AJQKwh2Kf
	xrPA9BnYWoZLvCCZZmwLZQfSBizmZ4ADPH2NhvAA/sUarQC9ZEsf974M+XxBB340
	=
Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com
Message-ID: <559D843E.5070402@cornell.edu>
Date: Wed, 08 Jul 2015 16:12:46 -0400
From: Ken Brown <kbrown@cornell.edu>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:31.0) Gecko/20100101 Thunderbird/31.7.0
MIME-Version: 1.0
To: cygwin@cygwin.com
Subject: Re: TEST RELEASE: Cygwin 2.1.0-0.4
References: <20150705213417.GH2918@calimero.vinschen.de> <70AD8D85-7D30-4894-857B-4FD12E55BBBE@etr-usa.com>
In-Reply-To: <70AD8D85-7D30-4894-857B-4FD12E55BBBE@etr-usa.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 8bit

On 7/8/2015 3:39 PM, Warren Young wrote:
> On Jul 5, 2015, at 3:34 PM, Corinna Vinschen <corinna-cygwin@cygwin.com> wrote:
>> ...RLIMIT_STACK...RLIM_INFINITY.
>
> This should fix the Emacs crash you reference later in this message without rebuilding Emacs, right?
>
> I’m not an Emacs user, as you know, but is there an STC for the Emacsizens to try on their systems?

There's no crash in the current Emacs release.  The crashes we were 
discussing were in my build of the current Emacs development trunk, 
which can use an alternate stack in order to recover from stack 
overflow.  This has no impact on users of the current Emacs release.

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