Mailing-List: contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT sources DOT redhat DOT com Delivered-To: mailing list cygwin AT sources DOT redhat DOT com Date: Wed, 7 Nov 2001 14:09:33 -0500 From: Christopher Faylor To: cygwin AT cygwin DOT com Subject: Re: 1.3.4: error in inheriting new PATH environment form WIN32 executable to cygwin executable Message-ID: <20011107140933.A5259@redhat.com> Reply-To: cygwin AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.3.21i On Wed, Nov 07, 2001 at 02:33:08PM +0100, Heiko_Elger AT arburg DOT com wrote: >Hello, > >I have the following problem: > >If a MS WIN 32 program changes his environment PATH variable to a very long >value (over 270 characters) and than calling a CYGWIN program per system() call >the path inside the CYGWIN program is reset to NULL! If it calls a MS WIN 32 >program all works fine. > >We have this problem with clearmake in exporting a very long path and the shell >is the CYGWIN sh.exe. > >I tried to reproduce it within a very small test. >I wrote two small programs (belwo you wil find the sourcecode): > changeenv.c --> MS WIN 32 program which change his PATH environment and calls >per system() the program "printpath" > printpath.c --> prints the PATH environment to stdout Cygwin expects path spec components will be no more than MAX_PATH in length. MAX_PATH == 260. This is a Microsoft constant. cgf -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Bug reporting: http://cygwin.com/bugs.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/