Closed kankri closed 1 year ago
Just a quick update: I fixed some of my errors in the source code and then reintroduced the scopequard::defer!{}
I had commented out, but rustc
was not panicking any more. Unfortunately I didn't save the exact source file which was causing the dump originally.
Another instance: https://github.com/rust-lang/rust/issues/63795
Would be great to find an example to reproduce this...
I ran into an ICE that appears to be the same as this one, since the error message also included thread 'rustc' panicked at 'no entry found for key'
.
I've reduced the code down to a single crate containing a single ~20 line source file, and a single direct external dependency, which still produces an ICE. The code is available here. It is probably possible to reduce this down further, but I think it's at the point where someone else could reasonably continue to investigate.
@Ryan1729: That example no longer ICEs on the latest nightly.
Just to be sure, I checked my earliest commit that had the ICE on the latest nightly, and it also does not show the ICE message either. So whatever was causing my issue does seem to have been fixed.
Triage: ICE fixed in nightly-2020-07-25, most likely by https://github.com/rust-lang/rust/pull/74703 since it fixed another issue with an "no entry found for key" ICE, namely https://github.com/rust-lang/rust/issues/74047. The fix added a regression test. Let's close this issue.
Got this error when running
cargo build
:The same command had been successful before, until it started failing consistently.
cargo clean
gave this error:I noticed "rls.exe" had that DLL loaded:
Next steps:
cargo build
: still fails the same waycargo clean
: no errorscargo build
: still fails the same waycargo build
: still fails the same waycargo clean
: no errorscargo build
: still fails the same wayAfter commenting out the body of
find_file_in_path
I could compile the code again and saw both withcargo build
and RLS a bunch of new errors which were not reported earlier. After fixing some of those I tried to selectively uncomment code infind_file_in_path
to see what triggers the problem. I found out that the culprit was use ofscopeguard::defer!{}
.I don't have a work-around for the
defer!
problem nor code I could share to repro the issue.It would be nice if the compiler wouldn't crash.