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:date:from:to:subject:message-id:reply-to
	:references:mime-version:content-type:in-reply-to; q=dns; s=
	default; b=gDQvmt6LQaijE2Fr2L3i4SL0fqOh5wONu7niwavpgOkNJgGb3W7NJ
	zERzL+T5QJrnkfjm+3vekltXQjQqOKnARPtKCKmXy1IPoNewDORaeLI4uzL65qWQ
	t7EsP7SK7gCbubSA00lbbow8ZDBXku+SrqTg117cTyjtbn2znBKu0E=
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:date:from:to:subject:message-id:reply-to
	:references:mime-version:content-type:in-reply-to; s=default;
	bh=pOHCR5pcq9B5fQ6xuoNO2yZX5xI=; b=cw3mWZ3zC0t9hDbVLZPPV/TqU4Sf
	PYXRU6ppoTzeGwLwBohZHyWYfHerYWcwxL4yzsJ7yYmcqEjJIvQ1dfoZYsjk48Pv
	w+jql22dghUvA2nKdyjpGXYzB7QlmngdoYTrnhp2AukT5NsAEqs3AGex+5v28Qga
	0GUiwBxxichT8JQ=
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=-5.9 required=5.0 tests=AWL,BAYES_00,RCVD_IN_DNSWL_NONE autolearn=ham version=3.3.2
X-HELO:	mho-01-ewr.mailhop.org
X-Mail-Handler:	Dyn Standard SMTP by Dyn
X-Report-Abuse-To:	abuse AT dyndns DOT com (see http://www.dyndns.com/services/sendlabs/outbound_abuse.html for abuse reporting information)
X-MHO-User:	U2FsdGVkX1+Aa/syUpMIVH7LMGV9hCeu
Date:	Tue, 8 Jul 2014 12:44:18 -0400
From:	Christopher Faylor <cgf-use-the-mailinglist-please AT cygwin DOT com>
To:	cygwin AT cygwin DOT com
Subject:	Re: Emacs-w32... Still Crashing
Message-ID:	<20140708164418.GA4963@ednor.casa.cgf.cx>
Reply-To:	cygwin AT cygwin DOT com
Mail-Followup-To:	cygwin AT cygwin DOT com
References:	<1404760352 DOT 3454 DOT YahooMailNeo AT web185401 DOT mail DOT gq1 DOT yahoo DOT com> <53BBF86B DOT 7090801 AT cornell DOT edu> <20140708150247 DOT GB2855 AT ednor DOT casa DOT cgf DOT cx> <53BC1DF7 DOT 1060701 AT cygwin DOT com>
MIME-Version:	1.0
In-Reply-To:	<53BC1DF7.1060701@cygwin.com>
User-Agent:	Mutt/1.5.20 (2009-06-14)

On Tue, Jul 08, 2014 at 11:36:07AM -0500, Yaakov Selkowitz wrote:
>On 2014-07-08 10:02, Christopher Faylor wrote:
>> On Tue, Jul 08, 2014 at 09:55:55AM -0400, Ken Brown wrote:
>>> Grasping at straws, as usual, I wonder if these mysterious crashes could
>>> be related to a bug that Corinna just fixed:
>>>
>>>    https://cygwin.com/ml/cygwin-cvs/2014-q3/msg00004.html
>>>
>>> Corinna, is this plausible?  If so, maybe Gustav should try the next
>>> snapshot of the Cygwin DLL.  (The current one doesn't seem to have this
>>> fix in it.)
>>
>> Actually, I was scratching my head over that change and wondering
>> what it was supposed to solve.
>
>We believe that this was the cause of e.g. mandb aborting on x86_64 
>without manually enlarging the stack commit size:

"We"?  Isn't that testable by setting the stack size down and putting a
printf in cygwin somewhere?

In any event, the comment in my code which is supposed to explain why
the tag is commented out is lacking details.  If this patch is a joint
effort then please add more details to the change that you made to my
code.

cgf

--
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 -