SIGSEGV error on release build (nightly) #125354
Comments
jnickg
added
C-bug
rustbot
added
the
needs-triage
|
Hmm, I can't seem to reproduce it. I'm building on commit Could you try building with the latest nightly? There was a recent LLVM update that fixed a reported segfault, although that one was on an M1 Macbook. |
jieyouxu
added
the
S-needs-repro
|
Updating to the latest changes behavior. The same segfault occurs, plus I get a new one!
New stack trace for existing segfault: Now I also get a segfault on this commit of another project I am working on, when running Stack trace: |
|
This is highly problematic for me as I need to be able to write/run bench tests which, as far as I know, require |
|
Hmm, unfortunately I can't seem to reproduce the segfault with this commit either. Do you happen to have any extra rustflags set in your Cargo's config.toml? Also, what's the last command that ends up running with |
|
I don't see any relevant In the
And in the
Is there any chance it is related to my specific CPU? I've occasionally seen SIGSEGV errors occur randomly in ways that were not reproducible, when building rust code. It seems more likely to crop up when building many crates at once, but when I run the same command to rebuild (after most crates built successfully), the crate that failed then succeeds without issue. Not worth filing a bug report for random failures, but I'm wondering if someone with an i9-14900K might have more luck reproducing it. |
|
FWIW I also can't reproduce this (on znver2). |
|
It should be noted that compiling rust can exercise the CPU more than a lot of other things and any errors are likely to be fatal in one way or another. It might be worth running a CPU test to see if there are any issues. You could also try downclocking to see if that helps. |
|
Hmm, that could be it (I'm on znver3). I found a comment from someone that's also been experiencing segfaults when compiling rust code on an i9-14900k. |
|
Just an update on my end: So far I have not found any faults in the CPU. The fact that That said, I have also observed a few (very rare) system crashes. I always chalked it up to system instability (I'm running Manjaro and, besides Linux/Arch having hiccups like that occasionally, I also have a lot of compute-heavy things installed and running). But I wouldn't say I've fully proven that it's NOT the CPU (yet). Any suggestions for good things to check related to finding potential CPU issues? |
|
You have a recent Intel CPU which is known to have bugs. Please, at minimum, adjust the power settings in your motherboard BIOS after updating it. You can choose to either follow your motherboard manufacturer's recommendations or listen to Intel.
This has also been fixed by downclocking the CPU. You can, of course, also attempt to get Intel, the motherboard manufacturer, or the vendor that sold you these things, to accept a return of their faulty merchandise. Closing this until it repros without a dodgy CPU. |
saethlin
added
C-discussion
Code
Failure occurs on this commit of a crate I am working on when running
cargo +nightly build --examples --release. Runningcargo +stable build --examples --releaseworks without issueMeta
lscpurustc --version --verbose:Error output
See backtrace for more info
Backtrace
The text was updated successfully, but these errors were encountered: