This is the mail archive of the
cygwin
mailing list for the Cygwin project.
Re: git fork failure on pull with a workaround (hopefully a clue for a fix)
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