-
Notifications
You must be signed in to change notification settings - Fork 13.4k
Build with memory sanitizer causes panic #102730
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
Labels
C-bug
Category: This is a bug.
E-needs-mcve
Call for participation: This issue has a repro, but needs a Minimal Complete and Verifiable Example
I-ICE
Issue: The compiler panicked, giving an Internal Compilation Error (ICE) ❄️
T-compiler
Relevant to the compiler team, which will review and decide on the PR/issue.
Comments
In case this helps out, I've also encountered this ICE when trying to use fuzzing for my own project (cg-jl/sawblade@8be5ef4). The command that I used was different, but causes the same panic in the same line: Code# git clone [email protected]:cybergsus/sawblade.git
# git checkout 8be5ef464ac842b55c2da87f4f0c666f373cdd11
# cd sawblade
RUSTFLAGS="-Zsanitizer=address" cargo +nightly fuzz build -Zbuild-std Meta
Error output
Backtrace (very similar, if not identical, to andreeaflorescu)
|
Duplicate of #101930 |
Fixed in #103950. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
C-bug
Category: This is a bug.
E-needs-mcve
Call for participation: This issue has a repro, but needs a Minimal Complete and Verifiable Example
I-ICE
Issue: The compiler panicked, giving an Internal Compilation Error (ICE) ❄️
T-compiler
Relevant to the compiler team, which will review and decide on the PR/issue.
Uh oh!
There was an error while loading. Please reload this page.
Code
This seems to happen when compiling rustc-std-workspace-core v1.99.0.
I am unsure what Rust code triggers this. I am running the following commands:
Meta
rustc --version --verbose
:I've tried the build with other nightly versions as well and it still fails but does not provide a stack trace.
Error output
Backtrace
The text was updated successfully, but these errors were encountered: