DomainKey-Signature: a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:message-id:subject:from:reply-to:to:date
	:in-reply-to:references:mime-version:content-type
	:content-transfer-encoding; q=dns; s=default; b=HoMMfEQ+pf8TfyXb
	JDWSJSL6K2gNpHYZW0heL9mCdHVHgnUCQMMVv1kUIRSGZCH4gkooLodCJ1/njgxf
	lMispqr9nqQkaQ8JJ43jl/nqUYN1P/dNdhoZkcH+yS2iGPxRsz3822Pi1ZCV945m
	XUcJ0Njk4Iqz1op+YGKLPAoL4D8=
Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com
Message-ID: <44c967db7f6941282c83a64ab4e966302379043a.camel@tdcadsl.dk>
Subject: Re: execvp* and spawnvp* react differently to same PATH environment variable
From: "Peter Dons Tychsen via cygwin" <cygwin@cygwin.com>
Reply-To: Peter Dons Tychsen <donpedro@tdcadsl.dk>
To: Ken Brown <kbrown@cornell.edu>, "cygwin@cygwin.com" <cygwin@cygwin.com>
Date: Thu, 10 Oct 2019 01:25:27 +0200
In-Reply-To: <d613e3c2-0420-2233-2b1e-77c704824b3d@cornell.edu>
References: <1549599310.1980812.1570481495155.JavaMail.zimbra@tdcadsl.dk>	<d613e3c2-0420-2233-2b1e-77c704824b3d@cornell.edu>
User-Agent: Evolution 3.30.5 (3.30.5-1.fc29)
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit

Hi Ken,

> I think you're probably right.  The use of FE_NNF in execvp* was
> introduced in 
> commit 6d63272b.  I suspect it was just an oversight that the spawvp*
> functions 
> weren't changed in the same way.  I'll send a patch to the cygwin-
> patches list 
> to fix this.  When Corinna returns, she can tell us whether there's
> some reason 
> that spawnvp should be different from execvp.

Excellent. Thanks for the fast response. I will keep an eye out for
when it lands.

Thanks,

/pedro

--
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