sigpipe ICE

[mahkoh]

~$ rustc | sh -c 'exec &0>-'
error: internal compiler error: unexpected failure
note: the compiler hit an unexpected failure path. this is a bug.
note: we would appreciate a bug report: http://doc.rust-lang.org/complement-bugreport.html
note: run with `RUST_BACKTRACE=1` for a backtrace
task '<main>' failed at 'failed printing to stdout: broken pipe (Broken pipe)', /build/rust-git/src/rust/src/libstd/io/stdio.rs:215

[pnkfelix]

This looks like a duplicate of #14505, which in turn was closed as a duplicate of #13824. Closing.

[pnkfelix]

Although I will admit that to me, #13824 is a debate about what our default interface should be for the standard library, which could be handled orthogonally to what rustc does internally for its output printing. I.e. perhaps #14505 should not have been closed as a duplicate in the first place.

@alexcrichton do you have any opinions here? (Reopening this ticket to encourage response.)

[alexcrichton]

I believe this is correct in failing the compiler with the question being whether it should ICE or not. I would think that it should try not to ICE, but not go to great lengths to do so (not worth a redesign or anything).

[frewsxcv]

visiting for triage

rustc 1.0.0-nightly (ba2f13ef0 2015-02-04 20:03:55 +0000)

This is still an issue. Error message is basically the same.

[mitsuhiko]

The more common form of exploring this is by piping into less and aborting:

-Z unstable-options --pretty=expanded|less

Then hit 'q':

error: internal compiler error: unexpected panic
note: the compiler unexpectedly panicked. this is a bug.
note: we would appreciate a bug report: <snip>
note: run with `RUST_BACKTRACE=1` for a backtrace
thread '<main>' panicked at 'failed printing to stdout: Broken pipe (os error 32)', ./stdio.rs:404