-
Notifications
You must be signed in to change notification settings - Fork 13.3k
ICE unwrap in compiler/rustc_hir/src/definitions.rs:452:14 #90715
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
Comments
Thanks for the bug report, @jbr! Do you by any chance also use |
@cjgillot, are we missing some kind dep-tracking that causes a query to be re-run even though one of its preconditions isn't met? |
@michaelwoerister yes, I believe we some dep-tracking here, but I have no idea which one beyond the usual suspects. The failing query is |
Print a backtrace when query forcing fails. The aim of this PR is to help debugging incremental compilation bugs where query forcing panics. For instance: rust-lang#90682 rust-lang#90697 rust-lang#90715 rust-lang#90739 rust-lang#91401 These bugs happen when the dep-graph attempts to force a dep-node whose fingerprint does not correspond to an actual DefPathHash. PR rust-lang#91741 attempts to hide this bug. I still don't know how to reproduce these bugs, so I sadly could not test this debugging device.
As this is from version 1.58, I am closing as a likely duplicate of one of these issues:
Several fixes were put in to place to resolve this, see the PRs: |
Print a backtrace when query forcing fails. The aim of this PR is to help debugging incremental compilation bugs where query forcing panics. For instance: rust-lang/rust#90682 rust-lang/rust#90697 rust-lang/rust#90715 rust-lang/rust#90739 rust-lang/rust#91401 These bugs happen when the dep-graph attempts to force a dep-node whose fingerprint does not correspond to an actual DefPathHash. PR rust-lang/rust#91741 attempts to hide this bug. I still don't know how to reproduce these bugs, so I sadly could not test this debugging device.
Print a backtrace when query forcing fails. The aim of this PR is to help debugging incremental compilation bugs where query forcing panics. For instance: rust-lang/rust#90682 rust-lang/rust#90697 rust-lang/rust#90715 rust-lang/rust#90739 rust-lang/rust#91401 These bugs happen when the dep-graph attempts to force a dep-node whose fingerprint does not correspond to an actual DefPathHash. PR rust-lang/rust#91741 attempts to hide this bug. I still don't know how to reproduce these bugs, so I sadly could not test this debugging device.
Print a backtrace when query forcing fails. The aim of this PR is to help debugging incremental compilation bugs where query forcing panics. For instance: rust-lang/rust#90682 rust-lang/rust#90697 rust-lang/rust#90715 rust-lang/rust#90739 rust-lang/rust#91401 These bugs happen when the dep-graph attempts to force a dep-node whose fingerprint does not correspond to an actual DefPathHash. PR rust-lang/rust#91741 attempts to hide this bug. I still don't know how to reproduce these bugs, so I sadly could not test this debugging device.
Code
Unfortunately I changed a lot of things in a large codebase and am not sure which resulted in this ICE, but thought I'd report anyway. Sorry and thanks!
Meta
rustc --version --verbose
:Error output
Backtrace
The text was updated successfully, but these errors were encountered: