-
Notifications
You must be signed in to change notification settings - Fork 13.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
ICE building panic_unwind (stage 1) in debug mode with incremental compilation #49153
Comments
There's a very high chance that this is fixed by #49079 |
I'll try to build the latest master and see what happens. |
@oli-obk Nope, just changed the file the error is emitted from. 😕
I have the backtrace here if you like but it's more than 100 frames deep so I don't know how much context you need. |
Thanks. I'll have a look. No need for a backtrace |
Repro: extern "C" {
pub static __ImageBase: u8;
}
pub static FOO: &'static u8 = unsafe { &__ImageBase }; The problem is that This is easy to fix :) |
…ster Encode/decode extern statics in metadata and incremental cache fixes #49153 cc @abonander r? @michaelwoerister incremental ICE
master
In
config.toml
:build.cargo
andbuild.rustc
to Rustup's proxiesrust.debug = true
(happens only in debug mode)codegen-units = 0
(specific value doesn't appear to affect the issue)x.py build
It gets to this point and ICEs:
I grepped the error message (
alloc id without corresponding allocation
) and it points to this line which appears to be associated with incremental compilation, which makes sense because this only triggers when building in debug mode and settingCARGO_INCREMENTAL=false
avoids the ICE.cc @alexcrichton rust-lang/cargo#4817
The text was updated successfully, but these errors were encountered: