This is the mail archive of the
mailing list for the Cygwin project.
Re: [1.7] gvim "Cannot fork" error
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
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.
Problem reports: http://cygwin.com/problems.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple