X-Recipient:	archive-cygwin AT delorie DOT com
X-SWARE-Spam-Status:	No, hits=-1.3 required=5.0 tests=AWL,BAYES_00,RCVD_IN_DNSWL_NONE,TW_YG,UNPARSEABLE_RELAY
X-Spam-Check-By:	sourceware.org
X-Yahoo-SMTP:	jenXL62swBAWhMTL3wnej93oaS0ClBQOAKs8jbEbx_o-
Date:	Mon, 11 Jul 2011 13:34:25 -0400
From:	Christopher Faylor <cgf-use-the-mailinglist-please AT cygwin DOT com>
To:	cygwin AT cygwin DOT com
Subject:	Re: Random fork failures
Message-ID:	<20110711173425.GA5484@ednor.casa.cgf.cx>
Reply-To:	cygwin AT cygwin DOT com
Mail-Followup-To:	cygwin AT cygwin DOT com
References:	<20110711082740 DOT GC8249 AT calimero DOT vinschen DOT de> <4E1AB60C DOT 7050902 AT gmail DOT com> <20110711090218 DOT GA22947 AT calimero DOT vinschen DOT de> <4E1AC212 DOT 7030806 AT gmail DOT com> <20110711095630 DOT GB22947 AT calimero DOT vinschen DOT de> <4E1ACF65 DOT 6070102 AT gmail DOT com> <20110711114747 DOT GD22947 AT calimero DOT vinschen DOT de> <20110711120430 DOT GE22947 AT calimero DOT vinschen DOT de> <4E1AFE3A DOT 4070406 AT gmail DOT com> <CAGHJv4dMnBfpM5jr_O8urBrpdbTD2+D2U1LVgwGJsEs471thyg AT mail DOT gmail DOT com>
MIME-Version:	1.0
In-Reply-To:	<CAGHJv4dMnBfpM5jr_O8urBrpdbTD2+D2U1LVgwGJsEs471thyg@mail.gmail.com>
User-Agent:	Mutt/1.5.20 (2009-06-14)
Mailing-List:	contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Id:	<cygwin.cygwin.com>
List-Unsubscribe:	<mailto:cygwin-unsubscribe-archive-cygwin=delorie DOT com AT cygwin DOT 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

On Mon, Jul 11, 2011 at 01:27:52PM -0400, Chris Sutcliffe wrote:
>On 11 July 2011 09:44, yoni levi wrote:
>>>> Actually, I have not the faintest idea. ?Can you build your own Cygwin
>>>> DLL without -O2, see if it still occurs, and run that scenario through
>>>> GDB?
>>>
>>> cygcheck -svr output as per http://cygwin.com/problems.html might give
>>> some clue as well...
>>>
>>>
>> Well, it works just fine with the debug (-O0) version.
>> With release (-02) version, it crashes (with my compilation, and with
>> snapshot from cygwin.com).
>
>Could this be another gcc 4.3.4 compiler issue (similar to the issue
>encountered with vim)?

Actually, I think it is more likely BLODA.

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 -