X-Recipient:	archive-cygwin AT delorie DOT com
X-SWARE-Spam-Status:	No, hits=-1.6 required=5.0 tests=AWL,BAYES_00,DKIM_SIGNED,DKIM_VALID,RCVD_IN_DNSWL_NONE,UNPARSEABLE_RELAY
X-Spam-Check-By:	sourceware.org
X-Yahoo-SMTP:	jenXL62swBAWhMTL3wnej93oaS0ClBQOAKs8jbEbx_o-
Date:	Mon, 14 Nov 2011 12:11:05 -0500
From:	Christopher Faylor <cgf-use-the-mailinglist-please AT cygwin DOT com>
To:	cygwin AT cygwin DOT com
Subject:	Re: fork problem on latest cygwin CVS
Message-ID:	<20111114171105.GA22991@ednor.casa.cgf.cx>
Reply-To:	cygwin AT cygwin DOT com
Mail-Followup-To:	cygwin AT cygwin DOT com
References:	<4EC12860 DOT 3050507 AT gmail DOT com> <20111114153109 DOT GA21295 AT ednor DOT casa DOT cgf DOT cx> <4EC13D23 DOT 8040705 AT gmail DOT com>
MIME-Version:	1.0
In-Reply-To:	<4EC13D23.8040705@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, Nov 14, 2011 at 05:09:07PM +0100, marco atzeri wrote:
>On 11/14/2011 4:31 PM, Christopher Faylor wrote:
>> On Mon, Nov 14, 2011 at 03:40:32PM +0100, marco atzeri wrote:
>>> Hi Cgf,
>>>
>>>
>>> after updating cygwin CVS build from
>>>    http://cygwin.com/ml/cygwin-cvs/2011-q4/msg00063.html
>>> to
>>>    http://cygwin.com/ml/cygwin-cvs/2011-q4/msg00064.html .. 66html
>>>
>>> on CYGWIN_NT-6.1-WOW64
>>>
>>> the shell have fork issues during  make/build session.
>>
>> Come on, you know the drill by now.  How about a simple test case?
>
>I know the drill, but I just updated from XP-32 to W7-64,
>one disk crashed, so I am reinstalling everything from scratch and
>taking a test case when building octave is never easy.
>
>So I need time to give you a simple test case, and eventually
>someone else will notice the same problem in advance.
>
>FYI 2011-11-08 snapshot does not suffer such problem.

FYI, the last thing any developer wants to hear after a major code
change is a generic "It's broke" report with no details and no way to
duplicate the problem.  A stack trace from a home-grown version of
cygwin1.dll is not a detail.  It's meaningless unless the addresses are
decoded.

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 -