Skip to content
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

internal compiler error: Error constructed but not emitted #62546

Closed
dwrensha opened this issue Jul 9, 2019 · 3 comments · Fixed by #62604
Closed

internal compiler error: Error constructed but not emitted #62546

dwrensha opened this issue Jul 9, 2019 · 3 comments · Fixed by #62604
Assignees
Labels
A-parser Area: The parsing of Rust source code to an AST E-needs-bisection Call for participation: This issue needs bisection: https://github.com/rust-lang/cargo-bisect-rustc I-ICE Issue: The compiler panicked, giving an Internal Compilation Error (ICE) ❄️ P-high High priority regression-from-stable-to-beta Performance or correctness regression from stable to beta. T-compiler Relevant to the compiler team, which will review and decide on the PR/issue.

Comments

@dwrensha
Copy link
Contributor

dwrensha commented Jul 9, 2019

I see the following error on the beta and nightly channels, but not on stable:

$ echo "pub t(#" > main.rs

$ rustc main.rs
error: this file contains an un-closed delimiter
 --> main.rs:1:9
  |
1 | pub t(#
  |      -  ^
  |      |
  |      un-closed delimiter

error: internal compiler error: Error constructed but not emitted

thread 'rustc' panicked at 'explicit panic', src/librustc_errors/diagnostic_builder.rs:387:13
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace.
error: aborting due to 2 previous errors


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

note: rustc 1.37.0-beta.2 (74e5a0d47 2019-07-08) running on x86_64-apple-darwin

Found with the help of libfuzzer-sys.

@Centril Centril added I-ICE Issue: The compiler panicked, giving an Internal Compilation Error (ICE) ❄️ T-compiler Relevant to the compiler team, which will review and decide on the PR/issue. A-parser Area: The parsing of Rust source code to an AST regression-from-stable-to-nightly Performance or correctness regression from stable to nightly. regression-from-stable-to-beta Performance or correctness regression from stable to beta. labels Jul 9, 2019
@pnkfelix pnkfelix added the E-needs-bisection Call for participation: This issue needs bisection: https://github.com/rust-lang/cargo-bisect-rustc label Jul 11, 2019
@pnkfelix
Copy link
Member

triage: P-high, because errors being swallowed, even in the presence of other errors, scares me a bit.

@pnkfelix pnkfelix added the P-high High priority label Jul 11, 2019
@nikomatsakis
Copy link
Contributor

Perhaps @estebank might be a good candidate to investigate?

@estebank estebank self-assigned this Jul 11, 2019
@estebank
Copy link
Contributor

estebank commented Jul 11, 2019

The error that is not being emitted is

error: expected `[`, found `)`
 --> file7.rs:1:8
  |
1 | pub t(#
  |        ^ expected `[`

Looking. Found, incoming PR shortly.

@estebank estebank removed the regression-from-stable-to-nightly Performance or correctness regression from stable to nightly. label Jul 13, 2019
Centril added a commit to Centril/rust that referenced this issue Jul 13, 2019
# for free to join this conversation on GitHub. Already have an account? # to comment
Labels
A-parser Area: The parsing of Rust source code to an AST E-needs-bisection Call for participation: This issue needs bisection: https://github.com/rust-lang/cargo-bisect-rustc I-ICE Issue: The compiler panicked, giving an Internal Compilation Error (ICE) ❄️ P-high High priority regression-from-stable-to-beta Performance or correctness regression from stable to beta. T-compiler Relevant to the compiler team, which will review and decide on the PR/issue.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

5 participants