public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Ken Brown <kbrown@cornell.edu>
To: cygwin@cygwin.com
Subject: Re: git -- error: cannot fork() for fetch-pack: Resource temporarily unavailable
Date: Sun, 18 Oct 2015 01:33:00 -0000	[thread overview]
Message-ID: <5622F6F6.8030303@cornell.edu> (raw)
In-Reply-To: <CAFLqW4NoEN0YOK1WDHxOWpmgH_SS=28jW3WzqQzgfW7K0f-Rrw@mail.gmail.com>

On 10/17/2015 8:32 PM, kuaf wrote:
> Hi list,
>
> The Cygwin was running on Windows 10 box based on the latest [setup-x86.exe][1].
> The unexpected error prompted when I `git clone` any repository,
>
>        0 [main] git-remote-https 24312 child_info_fork::abort:
> C:\cygwin\bin\cygcurl-4.dll: Loaded to different address:
> parent(0x580000) != child(0xCC0000)
> error: cannot fork() for fetch-pack: Resource temporarily unavailable

You need to do a full rebase (and possibly reboot) to fix this.  If you're not 
sure how to do a full rebase, see the following recent thread:

   https://www.cygwin.com/ml/cygwin/2015-10/msg00159.html

> With the `cygcheck git`, it showed a few api-ms-win-* missed, e.g.

> cygcheck: track_down: could not find api-ms-win-core-rtlsupport-l1-2-0.dll
[...]

These error messages are bogus.  They won't occur with the cygcheck in the next 
Cygwin release (or the current test release).

Ken

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

  reply	other threads:[~2015-10-18  1:33 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-10-18  0:32 kuaf
2015-10-18  1:33 ` Ken Brown [this message]
2015-10-18 11:36   ` kuaf

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=5622F6F6.8030303@cornell.edu \
    --to=kbrown@cornell.edu \
    --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).