Mailing-List: contact cygwin-help@sourceware.cygnus.com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@sources.redhat.com Delivered-To: mailing list cygwin@sources.redhat.com Date: Tue, 20 Nov 2001 14:11:34 -0500 From: Christopher Faylor To: cygwin@cygwin.com Subject: Re: 1.3.5: error in inheriting new PATH Message-ID: <20011120191134.GA12066@redhat.com> Reply-To: cygwin@cygwin.com Mail-Followup-To: cygwin@cygwin.com References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.3.23.1i On Tue, Nov 20, 2001 at 10:40:35AM +0100, Heiko_Elger@arburg.com wrote: >I'm sorry to post the same problem as in >http://sources.redhat.com/ml/cygwin/2001-11/msg00361.html again, but the answer >I was given in >http://sources.redhat.com/ml/cygwin/2001-11/msg00393.html could not be >the solution! > >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. If you set a component of the path to a very long value the results are undefined in cygwin. 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/