git fork failure on pull with a workaround (hopefully a clue for a fix)

[Christopher Faylor]

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