Mailing-List: contact cygwin-help@sourceware.cygnus.com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@sources.redhat.com Delivered-To: mailing list cygwin@sources.redhat.com Message-ID: <3BD44F40.9070202@ece.gatech.edu> Date: Mon, 22 Oct 2001 12:54:24 -0400 From: Charles Wilson User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:0.9.2) Gecko/20010726 Netscape6/6.1 X-Accept-Language: en-us MIME-Version: 1.0 To: cygwin@cygwin.com Subject: Re: more info on execvp problem References: <3BD3EA44.FF96A58A@syntrex.com> <20011022112817.C7609@redhat.com> <3BD43CF4.2611ABC3@syntrex.com> <3BD43DE9.9060205@ece.gatech.edu> <3BD43F41.6FCAFB94@syntrex.com> <20011022124707.A8721@redhat.com> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Christopher Faylor wrote: >>1. C directory C in current directory >>2. C: for drive C: root folder >> >>now put this path in PATH launch the debugger and see what is >>the output of getenv >> > > The light dawned. I finally understand. Sorry for being so dense. Me too. I didn't get it until now. (However, example (1. C directory....) is a bad security hole. relative paths in PATH is a *really* bad idea.) --Chuck -- 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/