From: jwe AT bevo DOT che DOT wisc DOT edu ("John W. Eaton")
Subject: b17 bash problem with /dev/null on Windows 95 system
7 Dec 1996 17:32:03 -0800
Sender: daemon AT cygnus DOT com
Approved: cygnus DOT gnu-win32 AT cygnus DOT com
Distribution: cygnus
Message-ID: <199612080022.SAA00871.cygnus.gnu-win32@tillamook-sharp.eaton.net>
Original-To: gnu-win32 AT cygnus DOT com
Original-Sender: owner-gnu-win32 AT cygnus DOT com

After installing all the binaries for b17 on a Windows 95 system, I
tried to run a configure script and got this:

  COPY FOR DUP FAILED, handle in FFFFFFFF 6!!
  bash.exe: /dev/null: Bad file number

Then I tried to echo something and redirect it to /dev/null with the
same results:

  bash$ echo foo > /dev/null
  COPY FOR DUP FAILED, handle in FFFFFFFF 6!!
  bash.exe: /dev/null: Bad file number

However,

  bash$ cat /dev/null

seems to do the right thing.

I don't have a directory called /dev.  (Should I?  Creating one didn't
seem to make any difference.)

I have the b17 version of bash installed as /bin/sh.  Nothing else is
in /bin.

I removed everything from b16 from /cygnus, and as far as I know, I
now have only b17 stuff installed.

Can anyone else reproduce this?  If so, do you know of a fix?  If not,
does anyone have suggestions about how to debug it?  Should I look at
bash or is the problem more likely in cygwin.dll?

Thanks,

jwe
-
For help on using this list, send a message to
"gnu-win32-request AT cygnus DOT com" with one line of text: "help".