From: Charles Wilson <cygwin@cwilson.fastmail.fm>
To: The Cygwin Mailing List <cygwin@cygwin.com>
Subject: Re: git svn fork() problems on cygwin 1.7.20
Date: Tue, 18 Jun 2013 21:25:00 -0000 [thread overview]
Message-ID: <51C0CFA4.4010607@cwilson.fastmail.fm> (raw)
In-Reply-To: <20130617144503.GF14578@lakka.kapsi.fi>
On 6/17/2013 10:45 AM, Mikko Rapeli wrote:
> On Mon, Jun 17, 2013 at 05:00:47PM +0300, Mikko Rapeli wrote:
>> Has anyone else seen these when using git svn or other perl programs
>> on cygwin 1.7.20?
> <snip>
>> $ git svn rebase
>> ...
>> 0 [main] perl 4424 child_info_fork::abort: address space needed by '_Client.dll' (0x520000) is already occupied
>
> Hmm. Searching for clues I saw this
> http://stackoverflow.com/questions/12042363/cygwin-git-fork-error-on-pull
>
> and tried out with minimal PATH:
>
> $ PATH=/bin:/usr/bin git svn rebase
> Current branch master is up to date.
>
> Default PATH on the machine includes various tools, compilers, CMake etc.
> Tried to bisect it but it seems that full long PATH has an 80% failure rate
> while mimal PATH=/bin/usr/bin has a 20% failure rate, but I could not identify
> which PATH component could be to blame.
See here:
http://www.cygwin.com/ml/cygwin-apps/2013-04/msg00342.html
and Corinna's reply:
"Do you have a big environment? Thre's a chance that the stack address
moves due to that."
--
Chuck
--
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
prev parent reply other threads:[~2013-06-18 21:22 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-17 14:05 Mikko Rapeli
2013-06-17 14:52 ` Mikko Rapeli
2013-06-17 15:18 ` Adam Dinwoodie
2013-06-18 10:11 ` Mikko Rapeli
2013-06-18 22:04 ` Larry Hall (Cygwin)
2013-06-20 10:53 ` Mikko Rapeli
2013-06-18 21:25 ` Charles Wilson [this message]
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=51C0CFA4.4010607@cwilson.fastmail.fm \
--to=cygwin@cwilson.fastmail.fm \
--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).