-
Notifications
You must be signed in to change notification settings - Fork 12.5k
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
RUST_BACKTRACE=full panic causes infinite loop on aarch64-pc-windows-msvc #123686
Comments
...huh. @dpaoliello I know you took a look at all this recently, do you have any insight? |
Sure, I can look into it |
I have a fix: rust-lang/backtrace-rs#610 |
matthiaskrgr
added a commit
to matthiaskrgr/rust
that referenced
this issue
Apr 13, 2024
Update backtrace submodule Fixes rust-lang#123686
rust-timer
added a commit
to rust-lang-ci/rust
that referenced
this issue
Apr 13, 2024
Rollup merge of rust-lang#123876 - dpaoliello:backtrace, r=ChrisDenton Update backtrace submodule Fixes rust-lang#123686
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I tried running this code (default
cargo new --bin
template, changedprintln!
topanic!
):It builds fine on a
aarch64-pc-windows-msvc
host, and runs fine withRUST_BACKTRACE
env variable:0
1
When I run it (on a
aarch64-pc-windows-msvc
host) with (RUST_BACKTRACE=full
), the panic triggers an infinite loop:This also causes unit test execution to hang (e.g. for
tokio
) ifRUST_BACKTRACE=full
and a document test contains ````should_panic`.rustc --version --verbose
:Additional Info:
aarch64-apple-darwin
.x86_64-pc-windows-msvc
.The text was updated successfully, but these errors were encountered: