Skip to content

rustc panics if outputting help message fails #36415

New issue

Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? # to your account

Closed
vi opened this issue Sep 12, 2016 · 3 comments
Closed

rustc panics if outputting help message fails #36415

vi opened this issue Sep 12, 2016 · 3 comments

Comments

@vi
Copy link
Contributor

vi commented Sep 12, 2016

$ rustc --help > /dev/full
error: internal compiler error: unexpected panic

note: the compiler unexpectedly panicked. this is a bug.

I stumbled upon it when tried rustc -Z help | grpe orbit

Version is rustc 1.13.0-nightly (1576de0ce 2016-08-21)

@vi
Copy link
Contributor Author

vi commented Sep 12, 2016

Related/dupe:

If this bug is WONTFIX then the compiler unexpectedly panicked. this is a bug. we would appreciate a bug report message should be inhibited for this particular case, or dupes will continue flowing.

@Mark-Simulacrum
Copy link
Member

So investigating this leads me to believe that we're handling something incorrectly here:

panic!("failed printing to {}: {}", label, e);
. The panic! seems to still be called despite the error being IO-related:

$ rustc -vV | test
error: internal compiler error: unexpected panic

note: the compiler unexpectedly panicked. this is a bug.

note: we would appreciate a bug report: https://github.com/rust-lang/rust/blob/master/CONTRIBUTING.md#bug-reports

thread 'rustc' panicked at 'failed printing to stdout: Broken pipe (os error 32)', src/libstd/io/stdio.rs:691
note: Run with `RUST_BACKTRACE=1` for a backtrace.

@Mark-Simulacrum
Copy link
Member

Closing in favor of #34376.

# for free to join this conversation on GitHub. Already have an account? # to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants