Re: bug in /bin/sh.exe (ash-20000823)

[Chris Faylor <cgf at cygnus dot com>]

On Fri, Sep 29, 2000 at 10:10:24PM +0200, Hubert Garavel wrote:
>
>Synopsis:
>---------
>
>        /bin/sh.exe fails to execute a binary program
>        that has no ".exe" extension, if the pathname
>        used to invoke his executable program contains
>        at least one slash.
>
>Comments:
>---------
>
>	This bug was observed both on Windows NT4 and 
>	Windows 2000 Professional.
>
>	This bug also occured with the previous version
>	of /bin/sh.exe
>
>        This bug does NOT occur with /bin/bash.exe
>
>How to reproduce the bug
>------------------------
>
>Open a Cygwin window and type 
>	/bin/sh
>to switch from bash to sh.
>
>Then, type
>
>cd /tmp
>
># part 1 of the test : files without any extension
>
>cp /bin/echo.exe mytest
>mytest 
>#	--> is OK if you have . in $PATH
>./mytest
>#	--> not OK : ./mytest: not found
>/tmp/mytest
>#	--> not OK : /tmp/mytest: not found

I can't explain the no path scenario but the basic problem is that
mytest doesn't have the executable bit set.  This is implied if you have
a .exe extension.  Otherwise it is off unless you're using CYGWIN=ntsec,
are running on an NTFS, and have done a 'chmod a+x mytest'.

cgf	

--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe@sourceware.cygnus.com