X-Recipient: archive-cygwin AT delorie DOT com
X-Spam-Check-By: sourceware.org
Date: Sun, 20 Sep 2009 22:24:57 -0400
From: Christopher Faylor <cgf-use-the-mailinglist-please AT cygwin DOT com>
To: cygwin AT cygwin DOT com
Subject: Re: [1.7] gvim "Cannot fork" error
Message-ID: <20090921022457.GA32232@ednor.casa.cgf.cx>
Reply-To: cygwin AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
References: <h8cl9e$pd1$1 AT ger DOT gmane DOT org>  <a9a39a210909120714n126aed2dpb7beead460a870b0 AT mail DOT gmail DOT com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <a9a39a210909120714n126aed2dpb7beead460a870b0@mail.gmail.com>
User-Agent: Mutt/1.5.20 (2009-06-14)
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
Precedence: bulk
List-Id: <cygwin.cygwin.com>
List-Unsubscribe: <mailto:cygwin-unsubscribe-archive-cygwin=delorie DOT com AT cygwin DOT com>
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Delivered-To: mailing list cygwin AT cygwin DOT com

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/

cgf

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