X-Recipient: archive-cygwin@delorie.com
X-Spam-Check-By: sourceware.org
From: "Dave Korn" <dave.korn@artimi.com>
To: <cygwin@cygwin.com>
References: <042c01c836a1$e6c0d1d0$2e08a8c0@CAM.ARTIMI.COM> <20071205123104.GH26345@calimero.vinschen.de> <04a001c8374f$a58b1a00$2e08a8c0@CAM.ARTIMI.COM> <20071205153214.GI26345@calimero.vinschen.de>
Subject: RE: Odd behaviour of __cygwin_environ?
Date: Wed, 5 Dec 2007 15:50:31 -0000
Message-ID: <04a801c83756$90a8b5f0$2e08a8c0@CAM.ARTIMI.COM>
MIME-Version: 1.0
Content-Type: text/plain; 	charset="US-ASCII"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Office Outlook 11
In-Reply-To: <20071205153214.GI26345@calimero.vinschen.de>
Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
Precedence: bulk
List-Id: <cygwin.cygwin.com>
List-Unsubscribe: <mailto:cygwin-unsubscribe-archive-cygwin=delorie.com@cygwin.com>
List-Subscribe: <mailto:cygwin-subscribe@cygwin.com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin@cygwin.com>
List-Help: <mailto:cygwin-help@cygwin.com>, <http://sourceware.org/ml/#faqs>
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com
Delivered-To: mailing list cygwin@cygwin.com

On 05 December 2007 15:32, Corinna Vinschen wrote:

> On Dec  5 15:00, Dave Korn wrote:
>> On 05 December 2007 12:31, Corinna Vinschen wrote:
>>> Keep in mind that the size of the
>>> native environment block is restricted to 32K.
>> 
>>   I thought when cygexec was in effect the posix environment and
>> commandline were passed around-behind-the-back-of CreateProcess, bypassing
>> that limit?  Or does it only handle the commandline but not environment?
> 
> It also handles the environment block.  Is there a native process in the
> call chain, maybe? 

  Nope, it's all cygwin through and through.  Big project using
make/gcc/binutils, nothing non-posix.

> If not, I don't see any other chance than to debug
> this further.  spawn_guts() and the build_env() functions might be good
> starting points for that.

  Thanks, that's what I'm trying right now.

  Disappointingly it disappears under strace.  That might have been down to
the strace-is-a-win32-process-launching-a-cygwin-process anomaly, which is why
I'm hacking about the dll.  Early results suggest that, even though I'm not
launching under strace, but instead enabling it (by calling strace.hello()
during initial_env() if I detect an environment variable in the win32
environment), the problem still disappears, which makes me suspicious of it
still being a race somehow.

    cheers,
      DaveK
-- 
Can't think of a witty .sigline today....


--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Problem reports:       http://cygwin.com/problems.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/

