Date: Fri, 23 Nov 2012 19:08:57 +0400
From: Andrey Repin <anrdaemon@freemail.ru>
Reply-To: Andrey Repin <cygwin@cygwin.com>
Message-ID: <269536431.20121123190857@mtu-net.ru>
To: Christopher Faylor <cygwin@cygwin.com>
Subject: Re: git fork failure on pull with a workaround (hopefully a clue for a fix)
In-Reply-To: <20121123134628.GA32195@ednor.casa.cgf.cx>
References: <509AB02F.1000300@kitware.com> <509AC4E0.2080709@bopp.net> <509BC18E.1050905@kitware.com> <20121123114127.GO17347@calimero.vinschen.de> <1429797465.20121123163258@mtu-net.ru> <20121123131123.GS17347@calimero.vinschen.de> <20121123134628.GA32195@ednor.casa.cgf.cx>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
Precedence: bulk
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com

Greetings, Christopher Faylor!

>>> > I *think* this is an issue between Windows and Cygwin for which there's
>>> > no easy solution.  The memory layout created by Windows can move the
>>> > main stack address in a child process depending on the size of the
>>> > environment.
>>> 
>>> > I observed this myself, but didn't find a way to fix it.  Maybe it's
>>> > related to the fact that Cygwin cleans out the Windows environment to a
>>> > bare minimum when forking.  This obviously results in a changed env.
>>> 
>>> Would it be meaningful to instrument this cause for easier tracking?
>>
>>I don't understand.

> Maybe it's an observation that we should somehow detect this in the
> forked child and give a clearer error message?

Something like that, if it is possible without much overhead or performance
loss.


--
WBR,
Andrey Repin (anrdaemon@freemail.ru) 23.11.2012, <19:08>

Sorry for my terrible english...


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