X-Recipient: archive-cygwin AT delorie DOT com X-SWARE-Spam-Status: No, hits=-1.3 required=5.0 tests=AWL,BAYES_00,SARE_MSGID_LONG40,SPF_PASS X-Spam-Check-By: sourceware.org MIME-Version: 1.0 In-Reply-To: References: Date: Sat, 12 Sep 2009 16:14:11 +0200 Message-ID: Subject: Re: [1.7] gvim "Cannot fork" error From: =?UTF-8?B?RnLDqWTDqXJpYyBCcm9u?= To: cygwin AT cygwin DOT com Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable X-IsSubscribed: yes Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm Precedence: bulk List-Id: List-Unsubscribe: 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 > I believe it worked fine before (until a few days ago). I updated to > latest cygwin by running setup-1.7.exe. > (Just running setup -> click several next... =C2=A0-> finish) > > And now if I do > =C2=A0 =C2=A0/bin/gvim > =C2=A0 =C2=A0:!ls > > I see a message 'Cannot fork' in the gvim window. > And see > =C2=A0 =C2=A02 [main] gvim 2092 fork: child -1 - died waiting for longjmp > =C2=A0 =C2=A0before initialization, retry 0, exit code 0xC0000005, errno = 11 > in the cygterm console window. > > If I run '/bin/gvim -f' (foreground), then '!ls' works fine. Exactly the same problem after recent update: Cannot fork and in the console -196297461 [main] gvim 5284 fork: child -1 - died waiting for longjmp before initialization, retry 0, exit code 0xC0000005, errno 11 Fr=C3=A9d=C3=A9ric -- 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