-
Notifications
You must be signed in to change notification settings - Fork 12.9k
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
SIGSEGV when compiling with 1.83.0 #134983
Comments
This looks like a hardware problem, you can find similar issues here: https://github.com/rust-lang/rust/issues?q=is%3Aissue%20label%3AC-defective-hardware%20 There are a few CPU models that are particularly prone to issues, but the indicator that this is a hardware problem not a bug in the Rust toolchain is that you are getting a variety of different backtraces from the crashes, and sometimes compilation succeeds. Hardware problems tend to surface under load, which the compiler tends to produce. |
We should probably have a debugging guide for these issues, considering we've been getting almost one every month since we added the label. memtest is often the starting point for diagnosing (for sure) that this is a hardware issue. There's no rush to close this issue until we're darn sure that this is a hardware issue, and not a bug. |
@traviscross Do you disagree with my statement above? |
I'm fairly certain that it's not a hardware issue; I've done a number of memtest, CPU stress tests, and GPU stress tests in the past couple of months to troubleshoot a (now fixed) thermal issue I was having, and none have ever turned up any bitflips or anything like that. |
Glossed over that bit. OK. Reopening. |
I reproduced it on WSL Ubuntu 22.04 |
I have left this running for 5 hours on my desktop in a clone of the above-linked repo on commit
(the |
Code
Unfortunately, this is just something that I experienced when compiling i3status-rs; I don't have a minimal code example and have not been able to reproduce in subsequent clean/build attempts, so I understand if this is closed as no repro, but I figured I'd share what I saw just in case it sparks something. The steps I took:
rustup
cargo install --path . --locked
Backtrace 1
(below).cargo install --path . --locked
Backtrace 2
(below).Backtrace 2
rustup
cargo install --path . --locked
- This was successfulrustup
cargo install --path . --locked
- This was successfulcargo install --path . --locked
- This was successfulAgain, I understand if this isn't enough info to successfully find a bug, but unfortunately it's all I've got. Every attempt I've made to repro since the initial backtraces has failed (ie, compiled successfully), including fully cleaning the repo and compiling completely from scratch.
Meta
rustc --version --verbose
:rustc 1.83.0 (90b35a6 2024-11-26)
binary: rustc
commit-hash: 90b35a6
commit-date: 2024-11-26
host: x86_64-unknown-linux-gnu
release: 1.83.0
LLVM version: 19.1.1
Error output
Backtrace 1 (Initial Build):
Backtrace 2 (Subsequent Builds):
The text was updated successfully, but these errors were encountered: