X-Recipient: archive-cygwin@delorie.com
X-SWARE-Spam-Status: No, hits=0.5 required=5.0	tests=AWL,BAYES_00,RCVD_IN_SORBS_WEB,RCVD_NUMERIC_HELO,SPF_HELO_PASS,T_RP_MATCHES_RCVD
X-Spam-Check-By: sourceware.org
To: cygwin@cygwin.com
From: Rolf Campbell <rcampbell-cygwin@dragonwaveinc.com>
Subject: Re: v1.7.10 -- forked process died unexpectedly
Date: Thu, 09 Feb 2012 15:51:38 -0500
Lines: 31
Message-ID: <jh1bla$299$1@dough.gmane.org>
References: <jgu7vd$b6u$1@dough.gmane.org> <4F32A5A3.3090404@gmail.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
User-Agent: Mozilla/5.0 (Windows NT 5.1; rv:10.0) Gecko/20120129 Thunderbird/10.0
In-Reply-To: <4F32A5A3.3090404@gmail.com>
X-IsSubscribed: yes
Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
Precedence: bulk
List-Id: <cygwin.cygwin.com>
List-Unsubscribe: <mailto:cygwin-unsubscribe-archive-cygwin=delorie.com@cygwin.com>
List-Subscribe: <mailto:cygwin-subscribe@cygwin.com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin@cygwin.com>
List-Help: <mailto:cygwin-help@cygwin.com>, <http://sourceware.org/ml/#faqs>
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com
Delivered-To: mailing list cygwin@cygwin.com

On 2012-02-08 11:41, marco atzeri wrote:
> On 2/8/2012 5:30 PM, Rolf Campbell wrote:
>> I get these sporadic failures in my build system after upgrading to
>> 1.7.10.  I can't reproduce these consistently, seems to happen randomly
>> every few dozen builds.
>>
>> mkdir -p output/device/1110/source/
>>        0 [main] make 7900 fork: child -1 - forked process died
>> unexpectedly, retry 0, exit code -1073741819, errno 11
>> make: vfork: Resource temporarily unavailable
>>
> 
> See
>   http://cygwin.com/faq.html
> at
>   4.44. How do I fix fork() failures?
> 
> and related
>   /usr/share/doc/rebase/README
> 
> Regards
> Marco

Yeah, I normally would rebaseall after seeing a forking issue, but this
one wasn't a familiar error message.  But I guess the new cygwin version
just has slightly different error messages to indicate a need for rebasing.

I don't know if this is a good idea, but what if this type of error
message included a suggestion to try "rebaseall"?  Might stop messages
like mine in the future.



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