We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
I tried this code:
large private repo.
But altered our Dockerfile as such: before: FROM rust:1.57.0 as base after: FROM rust:1.59.0 as base updating our rust version.
FROM rust:1.57.0 as base
FROM rust:1.59.0 as base
We use actix, and now cargo run --release results in the following soon after the web application starts:
cargo run --release
Illegal instruction
If we run locally (not docker) using cargo run --release we get a similar error:
[1] 43322 illegal hardware instruction cargo run --release
If we run locally not release cargo run we get the same error as above.
cargo run
I expected to see this happen: Virtually nothing changes, program operates as expected.
Instead, this happened: Illegal instruction
rustc --version --verbose:
rustc --version --verbose
rustc --version --verbose rustc 1.59.0 (9d1b2106e 2022-02-23) binary: rustc commit-hash: 9d1b2106e23b1abd32fce1f17267604a5102f57a commit-date: 2022-02-23 host: x86_64-apple-darwin release: 1.59.0 LLVM version: 13.0.0
No backtrace
thread panicked while processing panic. aborting. [1] 45675 illegal hardware instruction RUST_BACKTRACE=1 cargo run --release
The text was updated successfully, but these errors were encountered:
Found this though seems smaller in blast radius #82278
Sorry, something went wrong.
I think I may have isolated the issue. There was a recent update in our panic handling. It's possible that that is panicing itself.
Yes, my mistake. This is an issue internally. My hope would be that Rust could provide a clearer error message, but will close.
No branches or pull requests
I tried this code:
large private repo.
But altered our Dockerfile as such:
before:
FROM rust:1.57.0 as base
after:
FROM rust:1.59.0 as base
updating our rust version.
We use actix, and now
cargo run --release
results in the following soon after the web application starts:If we run locally (not docker) using
cargo run --release
we get a similar error:If we run locally not release
cargo run
we get the same error as above.I expected to see this happen:
Virtually nothing changes, program operates as expected.
Instead, this happened:
Illegal instruction
Meta
rustc --version --verbose
:No backtrace
The text was updated successfully, but these errors were encountered: