X-Recipient: archive-cygwin AT delorie DOT com X-SWARE-Spam-Status: No, hits=-1.7 required=5.0 tests=AWL,BAYES_00,DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,FREEMAIL_FROM,T_TO_NO_BRKTS_FREEMAIL X-Spam-Check-By: sourceware.org MIME-Version: 1.0 Date: Mon, 28 Jun 2010 17:36:04 +0100 Message-ID: Subject: 1.7.6 snapshot: intermittent "CreateProcessW failed" From: Andy Koppe To: cygwin AT cygwin DOT com Content-Type: text/plain; charset=UTF-8 X-IsSubscribed: yes Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com When running a couple of lengthy make-based builds in parallel, I eventually get error messages such as this: 3 [main] sh 4368 fork: child -1 - CreateProcessW failed, errno 2 /bin/sh: fork: No such file or directory 5 [main] make 5736 fork: child -1 - CreateProcessW failed, errno 2 make[2]: vfork: No such file or directory The errors aren't reproducible, i.e. when rerunning, one of the build fails elsewhere with the same sort of error. Hence I'm unable to provide a small testcase. It doesn't fail if I run just one build at a time, and it fails more quickly if I run more than two. I guess this suggests a synchronisation issue. This is on a 32-bit Windows XP. The issue didn't occur on 1.7.5 and before. I went back through previous snapshots to try to narrow to down the problem a little bit: 20100507 is fine, 20100518 is not. Andy -- 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