X-Recipient: archive-cygwin AT delorie DOT com X-Spam-Check-By: sourceware.org X-Authenticated: #3365661 Date: Thu, 8 May 2008 21:52:48 +0200 From: Thomas Plank To: cygwin AT cygwin DOT com Subject: Re: CreateProcessA failed, errno 11 Message-ID: <9069c4161d4f6017b25baf1441231ed8@tp.myfqdn.de> References: <2fde52201f6a45740e533f30c17cd4a0 AT tp DOT myfqdn DOT de> <481A28C8 DOT 3000301 AT acm DOT org> Lines: 16 X-Y-GMX-Trusted: 0 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 Brian Ford wrote: > On Thu, 1 May 2008, David Rothenberger wrote: >> I had the same issue and just tracked it down to the ATI Catalyst 8.3 >> and 8.4 drivers. I had no problem with the 7.10 version, but with both >> 8.3 and 8.4, my PIDs were never reused and doing a large compile (in my >> case, subversion) would cause the error you mentioned. > ATI is aware of the bug. Me too ;-). I just want to inform all other affected by this driver debacle: I installed driver version 7.12 (still downloadable from AMD aka ATI) and the fork() errors disappeared as well as memory faults with Windows. -- mfg Thomas -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/