This is the mail archive of the
cygwin-developers
mailing list for the Cygwin project.
Re: execvp() runs programs from cwd even if '.' is not in PATH
- From: Corinna Vinschen <corinna-cygwin at cygwin dot com>
- To: cygwin-developers at cygwin dot com
- Date: Mon, 21 Dec 2009 16:16:45 +0100
- Subject: Re: execvp() runs programs from cwd even if '.' is not in PATH
- References: <1NBPAK-1lORIe0@fwd05.aul.t-online.de> <20091120105935.GS29173@calimero.vinschen.de> <4B2A394F.7090305@byu.net> <20091217142810.GX8059@calimero.vinschen.de>
- Reply-to: cygwin-developers at cygwin dot com
On Dec 17 15:28, Corinna Vinschen wrote:
> On Dec 17 06:59, Eric Blake wrote:
> > According to Corinna Vinschen on 11/20/2009 3:59 AM:
> > > On Nov 20 09:48, Christian Franke wrote:
> > >> execvp() and the other 'p' variants of exec run programs also from
> > >> current directory even if '.' is not in the PATH.
> > >
> > > If Cygwin doesn't find the executable in $PATH, the string is used
> > > literally when calling spawn_guts, which in turn converts the incoming
> > > path to an absolute Windows path, which obviously works fine.
> > >
> > > This is a bug and the fix is easy, but it's not a regression, so we
> > > should better stick to it until after 1.7.1.
> >
> > Are you planning on checking in the fix now?
>
> Not yet since I have other things on my plate. Actually, if you
> have a patch handy, feel free to send it to the patches list.
Should be fixed in CVS now.
Corinna
--
Corinna Vinschen Please, send mails regarding Cygwin to
Cygwin Project Co-Leader cygwin AT cygwin DOT com
Red Hat