Date: Fri, 23 Nov 2012 08:46:28 -0500
From: Christopher Faylor <cgf-use-the-mailinglist-please AT cygwin DOT com>
To: cygwin AT cygwin DOT com
Subject: Re: git fork failure on pull with a workaround (hopefully a clue for a fix)
Message-ID: <20121123134628.GA32195@ednor.casa.cgf.cx>
Reply-To: cygwin AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
References: <509AB02F DOT 1000300 AT kitware DOT com> <509AC4E0 DOT 2080709 AT bopp DOT net> <509BC18E DOT 1050905 AT kitware DOT com> <20121123114127 DOT GO17347 AT calimero DOT vinschen DOT de> <1429797465 DOT 20121123163258 AT mtu-net DOT ru> <20121123131123 DOT GS17347 AT calimero DOT vinschen DOT de>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20121123131123.GS17347@calimero.vinschen.de>
User-Agent: Mutt/1.5.20 (2009-06-14)
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
Precedence: bulk
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com

On Fri, Nov 23, 2012 at 02:11:23PM +0100, Corinna Vinschen wrote:
>On Nov 23 16:32, Andrey Repin wrote:
>> > 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?

cgf

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