delorie.com/archives/browse.cgi | search |
X-Recipient: | archive-cygwin AT delorie DOT com |
X-SWARE-Spam-Status: | No, hits=0.7 required=5.0 tests=AWL,BAYES_00,FREEMAIL_FROM,KAM_THEBAT,KHOP_THREADED,SPF_SOFTFAIL |
X-Spam-Check-By: | sourceware.org |
Date: | Fri, 23 Nov 2012 19:08:57 +0400 |
From: | Andrey Repin <anrdaemon AT freemail DOT ru> |
Reply-To: | Andrey Repin <cygwin AT cygwin DOT com> |
Message-ID: | <269536431.20121123190857@mtu-net.ru> |
To: | Christopher Faylor <cygwin AT cygwin DOT 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 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> <20121123134628 DOT GA32195 AT ednor DOT casa DOT cgf DOT cx> |
MIME-Version: | 1.0 |
X-IsSubscribed: | yes |
Mailing-List: | contact cygwin-help AT cygwin DOT com; run by ezmlm |
List-Id: | <cygwin.cygwin.com> |
List-Unsubscribe: | <mailto:cygwin-unsubscribe-archive-cygwin=delorie DOT com AT cygwin DOT com> |
List-Subscribe: | <mailto:cygwin-subscribe AT cygwin DOT com> |
List-Archive: | <http://sourceware.org/ml/cygwin/> |
List-Post: | <mailto:cygwin AT cygwin DOT com> |
List-Help: | <mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs> |
Sender: | cygwin-owner AT cygwin DOT com |
Mail-Followup-To: | cygwin AT cygwin DOT com |
Delivered-To: | mailing list cygwin AT cygwin DOT 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 AT freemail DOT 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
webmaster | delorie software privacy |
Copyright © 2019 by DJ Delorie | Updated Jul 2019 |