This is the mail archive of the
mailing list for the Cygwin project.
Re: bug in /bin/sh.exe (ash-20000823)
- To: cygwin at sources dot redhat dot com
- Subject: Re: bug in /bin/sh.exe (ash-20000823)
- From: Chris Faylor <cgf at cygnus dot com>
- Date: Fri, 29 Sep 2000 16:35:16 -0400
- References: <200009292010.WAA14437@noisetier.inrialpes.fr>
- Reply-To: cygwin at sources dot redhat dot com
On Fri, Sep 29, 2000 at 10:10:24PM +0200, Hubert Garavel wrote:
> /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.
> 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
>to switch from bash to sh.
># part 1 of the test : files without any extension
>cp /bin/echo.exe mytest
># --> is OK if you have . in $PATH
># --> not OK : ./mytest: not found
># --> 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'.
Want to unsubscribe from this list?
Send a message to email@example.com