From:	cgf AT cygnus DOT com (Christopher Faylor)
Subject:	Re: script execution bug
22 Nov 1998 20:37:41 -0800 :
Message-ID:	<19981122232419.B4061.cygnus.cygwin32.developers@cygnus.com>
References:	<uww4qtsxk DOT fsf AT parvati DOT will DOT or DOT jp>
Mime-Version:	1.0
To:	Kazuhiro Fujieda <fujieda AT jaist DOT ac DOT jp>, cygwin32-developers AT cygnus DOT com

On Sun, Nov 22, 1998 at 07:08:13PM +0900, Kazuhiro Fujieda wrote:
>>>> On Fri, 20 Nov 1998 14:20:57 -0500
>>>> Christopher Faylor <cgf AT cygnus DOT com> said:
>
>> I agree that what cygwin is doing is not POSIX but we apparently
>> now have a number of people on the mailing list using this
>> "feature" so I don't believe that we can remove it without
>> generating a lot of confusion and dissatisfaction.
>
>I don't think so because this feature have been enabled just
>only 10 days ago, but I can accept your decision.

As far as I can tell, that find_exec has been in there for at least a
year.  People on the gnu-win32 mailing list were complaining that this
feature was broken when B20 was released.

>> Does the patch below solve the problem?
>(snip)
>
>This patch solve the null pointer dereference, but can't solve
>another problem pointed out in the latter half of my last mail
>cited below.
>
>>>> On 20 Nov 1998 22:06:15 +0900
>>>> Kazuhiro Fujieda <fujieda AT jaist DOT ac DOT jp> said:
>
>> Then, when a script of which interpreter is also a script is
>> executed, the interpreter of the latter script is executed with
>> odd arguments.
>> 
>> For example,
>> $ echo '#!/usr/local/bin/bar' > /usr/local/bin/foo
>> $ echo '#!/sh' > /usr/local/bin/bar
>> $ /usr/local/bin/foo
>> /usr/local/bin/C:\usr\local\bin\bar: Can't open /usr/local/bin/C:\usr\local\bin\bar

Sorry.  I forgot to check this.

cgf

- Raw text -