www.delorie.com/archives/browse.cgi   search  
Mail Archives: cygwin-developers/1998/09/29/02:11:00

From: corinna DOT vinschen AT cityweb DOT de (Corinna Vinschen)
Subject: b20 alpha
29 Sep 1998 02:11:00 -0700 :
Message-ID: <3610A3BB.77F10FDC.cygnus.cygwin32.developers@cityweb.de>
Mime-Version: 1.0
To: cygwin32-developers AT cygnus DOT com

I have a funny effect with b20 cygwin.dll.
It only happens in bash, not in tcsh and it
only comes to pass, if CYGWIN32=tty.

First try:
    bash-2.01$ echo x | cat
    x

Second try:
    bash-2.01$ echo x > foo
    bash-2.01$ echo x | cat
    cat: standard output: Bad file number

This doesn't take place in the following example:
    bash-2.01$ cat file > foo
    bash-2.01$ cat file | cat

But here:
    bash-2.01$ echo x > foo
    bash-2.01$ cat file | cat
    cat: standard output: Bad file number

After the first stdout redirection of a shell builtin,
the pipes doesn't work anymore. I have tried a
	STRACE='0xff:0,xxx'
and I have found the following strange lines in the output:
    ...
    [main] cat 1037 (0) hinfo::de_linearize_fd_array: closed fd 1
    ...
    [main] cat 1037 (0) _fstat: -1 = fstat (1, 0x240FF04)
    ...

Stdout shouldn't be closed, should it?

BTW I have compiled the dll as `cygwinb19.dll', to avoid
recompilation of all tools.

Corinna

- Raw text -


  webmaster     delorie software   privacy  
  Copyright © 2019   by DJ Delorie     Updated Jul 2019