From: Cesar Strauss <cestrauss@gmail.com>
To: cygwin@cygwin.com
Subject: Re: [1.7] gvim "Cannot fork" error
Date: Mon, 21 Sep 2009 03:00:00 -0000 [thread overview]
Message-ID: <h96q72$4dd$1@ger.gmane.org> (raw)
In-Reply-To: <20090921022457.GA32232@ednor.casa.cgf.cx>
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
next prev parent reply other threads:[~2009-09-21 3:00 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-11 4:57 SungHyun Nam
2009-09-12 14:14 ` Frédéric Bron
2009-09-21 2:25 ` Christopher Faylor
2009-09-21 3:00 ` Cesar Strauss [this message]
2009-09-21 6:06 ` SungHyun Nam
2009-09-21 7:51 ` Yaakov (Cygwin/X)
2009-09-21 14:48 ` Christopher Faylor
2009-09-21 15:59 ` Dave Korn
2009-09-21 18:38 ` Christopher Faylor
2009-09-21 23:42 ` Yaakov (Cygwin/X)
2009-09-22 2:10 ` Christopher Faylor
2009-09-25 0:40 Angelo Graziosi
2009-09-25 1:30 ` Christopher Faylor
2009-09-25 1:40 ` Christopher Faylor
2009-09-25 3:22 ` Yaakov (Cygwin/X)
2009-09-25 8:30 Angelo Graziosi
2009-09-25 13:50 ` Christopher Faylor
2009-09-25 8:54 Angelo Graziosi
2009-09-25 13:19 ` Ken Brown
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='h96q72$4dd$1@ger.gmane.org' \
--to=cestrauss@gmail.com \
--cc=cygwin@cygwin.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).