DomainKey-Signature: a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:from:to:subject:date:message-id:references
	:in-reply-to:content-type:content-id:content-transfer-encoding
	:mime-version; q=dns; s=default; b=MrMNWxWxPDrXcGYYVAY4R5AYNaXT/
	GvP6eJYVhk8aBAg1NwcKINIoDGfPaXzMPrQlr+++6BDrLRiWatCuG/scAkH7NT+H
	VMO4t4Ouarps96MhamJCWamNE5DUkl1O/geZz7KfTy2RiPCITdzlozT+G6ialZqi
	3czsWJxen5XS4U=
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
From: Ken Brown <kbrown AT cornell DOT edu>
To: "cygwin AT cygwin DOT com" <cygwin AT cygwin DOT com>
Subject: Re: execvp* and spawnvp* react differently to same PATH environment variable
Date: Wed, 9 Oct 2019 16:43:08 +0000
Message-ID: <d613e3c2-0420-2233-2b1e-77c704824b3d@cornell.edu>
References: <1549599310 DOT 1980812 DOT 1570481495155 DOT JavaMail DOT zimbra AT tdcadsl DOT dk>
In-Reply-To: <1549599310.1980812.1570481495155.JavaMail.zimbra@tdcadsl.dk>
user-agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:60.0) Gecko/20100101 Thunderbird/60.9.0
received-spf: None (protection.outlook.com: cornell.edu does not designate permitted sender hosts)
Content-Type: text/plain; charset="Windows-1252"
Content-ID: <3A35FB5557181241A9F375984157E956 AT namprd04 DOT prod DOT outlook DOT com>
MIME-Version: 1.0
X-MS-Exchange-CrossTenant-userprincipalname: 7om4vAUc8UIm1NnZ+0rsNb8X5c+daqXevgu71wFcLHShGbsWYNFR1jAT45A8aPAQbKiwa1Z+RtQJVh79gBZvcw==
X-IsSubscribed: yes
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by delorie.com id x99Ghi5m006111

On 10/7/2019 4:51 PM, donpedro.tdcadsl.dk via cygwin wrote:
> Hi all,
> 
> While working on something i noticed that execvp* and spawnvp* behave differently with regards to $PATH, which i think is not correct.
> 
> ----------------------------------------------
> 
> 1) The execvp* functions are called like this:
> 
> return spawnve ( _P_OVERLAY | _P_PATH_TYPE_EXEC ,
>     find_exec ( file , buf , "PATH" , FE_NNF ) ? : "" ,
>     argv , envp );
> 
> This calls find_exec() with FE_NNF, which causes the path to be NULL if not found in $PATH.
> 
> This later causes cygwin to fail correctly if the program is not in $PATH.
> 
> ----------------------------------------------
> 
> 2) The spawnvp* functions are called like this:
> 
> return spawnve (mode | _P_PATH_TYPE_EXEC, find_exec (file, buf), argv, cur_environ ());
> 
> This does _not_ calls find_exec() with FE_NNF which causes the path to be the posix form, as it is not found in path.
> 
> This later causes cygwin to find the program even though it was not in $PATH which seems wrong.
> 
> ----------------------------------------------
> 
> This seems like a bug in spawnvp* functions unless i am missing something?

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.

Ken

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