Re: ignored SIGPIPE (Darwin vs. cat)

2009-03-04 Thread Bruno Haible
Eric Blake wrote: > you can often write > tests in such a way that you can guarantee the reader will consume all > input until the writer has completed, rather than completing early, to > avoid the issue of whether SIGPIPE is ignored. I want to avoid the extra effort to inspect all unit tests one

Re: ignored SIGPIPE (Darwin vs. cat)

2009-03-03 Thread Eric Blake
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 According to Bruno Haible on 3/3/2009 5:37 PM: > Eric Blake wrote: >> When running test-closein.sh, I'm getting spurious output on Darwin: >> >> cat: standard output: Bad file descriptor >> PASS: test-closein.sh > > How to reproduce? $ uname -r 8.11.

Re: ignored SIGPIPE (Darwin vs. cat)

2009-03-03 Thread Bruno Haible
Eric Blake wrote: > When running test-closein.sh, I'm getting spurious output on Darwin: > > cat: standard output: Bad file descriptor > PASS: test-closein.sh How to reproduce? On Darwin 7 and 9 (MacOS X 10.3.x and 10.9.x) I reproduce an error from $ cat foo | : or $ { sleep 1; cat foo; } | :

Re: Darwin vs. cat

2009-03-03 Thread Jim Meyering
Eric Blake wrote: > When running test-closein.sh, I'm getting spurious output on Darwin: > > cat: standard output: Bad file descriptor > PASS: test-closein.sh > > $ cat --version | head -n 1 > cat (GNU coreutils) 7.1 > $ uname -v > Darwin Kernel Version 8.11.0: Wed Oct 10 18:26:00 PDT 2007; > root:

Darwin vs. cat

2009-03-03 Thread Eric Blake
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 When running test-closein.sh, I'm getting spurious output on Darwin: cat: standard output: Bad file descriptor PASS: test-closein.sh $ cat --version | head -n 1 cat (GNU coreutils) 7.1 $ uname -v Darwin Kernel Version 8.11.0: Wed Oct 10 18:26:00 PDT