X-Recipient: archive-cygwin@delorie.com X-SWARE-Spam-Status: No, hits=-1.3 required=5.0 tests=AWL,BAYES_00,RCVD_NUMERIC_HELO,SPF_HELO_PASS,SPF_PASS X-Spam-Check-By: sourceware.org To: cygwin@cygwin.com From: Cesar Strauss Subject: Re: [1.7] gvim "Cannot fork" error Date: Sun, 20 Sep 2009 23:59:49 -0300 Lines: 40 Message-ID: References: <20090921022457.GA32232@ednor.casa.cgf.cx> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit User-Agent: Thunderbird 2.0.0.23 (Windows/20090812) In-Reply-To: <20090921022457.GA32232@ednor.casa.cgf.cx> X-IsSubscribed: yes Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm Precedence: bulk List-Id: List-Unsubscribe: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com Delivered-To: mailing list cygwin@cygwin.com Christopher Faylor wrote: > On Sat, Sep 12, 2009 at 04:14:11PM +0200, Fr??d??ric Bron wrote: >>> 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... ??-> finish) >>> >>> And now if I do >>> ?? ??/bin/gvim >>> ?? ??:!ls >>> >>> I see a message 'Cannot fork' in the gvim window. >>> And see >>> ?? ??2 [main] gvim 2092 fork: child -1 - died waiting for longjmp >>> ?? ??before 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 > > This should be fixed in the next Cygwin snapshot and, subsequently, in the > next release. > > If you could test this and confirm that the snapshot fixes the problem I'll > roll a new release. It turns out to be a pretty serious bug. > > http://cygwin.com/snapshots/ > I am not the OP, but I could reproduce the problem, and I confirm it is fixed on today's snapshot (20090920). Furthermore, it solves another issue I posted myself: http://cygwin.com/ml/cygwin-xfree/2009-09/msg00051.html Many thanks! Regards, Cesar -- 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