X-Spam-Check-By: sourceware.org Date: Wed, 2 Aug 2006 11:12:59 -0400 From: Christopher Faylor To: cygwin AT cygwin DOT com Subject: Re: Cygwin 1.5.21 execvp fails when Windows PATH has empty element Message-ID: <20060802151259.GA19530@trixie.casa.cgf.cx> Reply-To: cygwin AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com References: <3 DOT 0 DOT 5 DOT 32 DOT 20060802022919 DOT 01f39370 AT mailer> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <3.0.5.32.20060802022919.01f39370@mailer> User-Agent: Mutt/1.5.11 Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm Precedence: bulk List-Unsubscribe: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com On Wed, Aug 02, 2006 at 02:29:19AM -0400, Steven Doerfler wrote: >A Cygwin program run from cmd.exe fails to invoke another Cygwin via the >PATH, when the PATH contains an empty entry. > >Is this a known bug? Thanks in advance for any responses. It's not a known bug but it is now fixed in CVS. Thanks for the test case. When we start up snapshots again, this will also be fixed in a snapshot at http://cygwin.com/snapshots/ . cgf -- 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/