Mailing-List: contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT sources DOT redhat DOT com>
List-Archive: <http://sources.redhat.com/ml/cygwin/>
List-Post: <mailto:cygwin AT sources DOT redhat DOT com>
List-Help: <mailto:cygwin-help AT sources DOT redhat DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender: cygwin-owner AT sources DOT redhat DOT com
Delivered-To: mailing list cygwin AT sources DOT redhat DOT com
Message-ID: <3BCEF347.31A0D7D8@syntrex.com>
Date: Thu, 18 Oct 2001 17:20:39 +0200
From: Pavel Tsekov <ptsekov AT syntrex DOT com>
Organization: Syntrex Inc.
X-Mailer: Mozilla 4.76 [en] (X11; U; Linux 2.4.2-2 i686)
X-Accept-Language: en
MIME-Version: 1.0
To: cygwin AT cygwin DOT com
Subject: [Fwd: simple execvp test]
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

Pavel Tsekov wrote:
> 
> This mail is inspired by an offlist discussion
> with James Lee about vi execution before
> "cvs commit" command.
> 
> Given the following simple test he says nothing
> happens after he executes it, as happens with the
> "cvs commit" command which fails to execute vi
> with the following error code "cannot exec vi: No such file or
> directory".
> 
> #include <unistd.h>
> 
> int main()
> {
>   char *arg[] = {
>     0
>   };
> 
>   execvp("vi", arg);
> 
>   return 0;
> }
> 
> If he sets for example the EDITOR variable
> to /usr/bin/vi then cvs suceeds in executing
> vi.
> 
> So is this a known problem with execvp assuming
> that it should search the path for the executable.

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