From: cgf AT cygnus DOT com (Christopher Faylor)
Subject: Re: B20, bash, #! & relative script execution
20 Nov 1998 09:07:44 -0800
Message-ID: <19981120114605.F20182.cygnus.cygwin32.developers@cygnus.com>
References: <000001be1485$514e89a0$010120c0 AT menpc1>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
To: Austin David France <adf AT mentor-systems DOT com>,
        cygwin32-developers AT cygnus DOT com

On Fri, Nov 20, 1998 at 12:57:23PM -0000, Austin David France wrote:
>B20.0 (0.1/1/1) -11-8 11:59:08
>Bash 2.02.1(2)
>PATH=/e/gnuwin32/CYGWIN~1/H-I586~1/bin:/c/winnt/system32:/d/mentor/bin
>NTW40SP4
>
>I have a script called "xx" in /d/Mentor/Bin
>
>   #!/bin/bash
>   echo $@
>
>>From the bash command line, if I type "xx", nothing happens - bash hangs -
>until I hit ^c
>
>The last few cygwin1.dll traces output by this are:
>--------------------------------------------------------------------------
>[main] bash 1001 (0) find_exec:
>e:\GnuWin32\cygwin-b20\H-i586-cygwin32\bin\bash.exe = find_exec (/bin/bash)
>[main] bash 1001 (0) spawn_guts: getting path of /d/mentor/bin/xx
>[main] bash 1001 (0) spawn_guts: path is
>[sig] bash 1001 (0) wait_sig: sigcatch_nonmain 0x15
>----------------------------------------------------------------------------

Please try this with a recent snapshot, if you haven't already.

When reporting bugs like this it is very important to provide
complete information.  We now have a program "cygcheck" which
will provide this.  So, include cygcheck output with your
bug report.

Thanks,
Chris