Re: bash crashes with named pipes

[Kevin]

Thanks, I understand.

The printout
Warning: Program '/bin/bash' crashed.
seems misleading. To me, it implies that bash did something wrong due to a bug 
in bash, which is why I submitted a bug report.
An error message that a SIGPIPE was received would be more helpful.
I also don't think an interactive bash session should ever crash. I'm not sure 
how a non-interactive session should behave.

just my 2 cents

Cheers
Kevin

> On 6/11/10 5:10 PM, Kevin wrote:
> > Maybe I'm doing something wrong, but the following will make bash
> > crash.
> > 
> > 
> > terminal 2:
> > $ mkfifo test
> > $ while true; do echo foo && sleep 1; done > test
> > 
> > terminal 1:
> > $ <test cat
> > 
> > wait for a few "foo"s to be printed and then kill with ctrl-c
> > terminal 2 will read:
> > 
> > Warning: Program '/bin/bash' crashed.
> 
> Bash gets a SIGPIPE and exits, since that's a fatal signal.  The question
> is whether it should try and figure out whether the file it's writing to
> is a pipe and catch and discard SIGPIPE if so.
> 
> Chet
>