-
Notifications
You must be signed in to change notification settings - Fork 13k
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
Regression: .format
from itertools
started runtime panicking with rustc 1.71.0
#110717
Labels
A-runtime
Area: std's runtime and "pre-main" init for handling backtraces, unwinds, stack overflows
C-bug
Category: This is a bug.
regression-from-stable-to-nightly
Performance or correctness regression from stable to nightly.
T-libs
Relevant to the library team, which will review and decide on the PR/issue.
Comments
flip1995
added
regression-from-stable-to-nightly
Performance or correctness regression from stable to nightly.
C-bug
Category: This is a bug.
labels
Apr 23, 2023
rustbot
added
the
I-prioritize
Issue: Indicates that prioritization has been requested for this issue.
label
Apr 23, 2023
I'll look into this tomorrow. Can you check if it also happens with -Zflatten-format-args=no? |
This is unrelated to |
matthiaskrgr
added a commit
to matthiaskrgr/rust
that referenced
this issue
Apr 24, 2023
format panic message only once For `panic!` and friends, the `std` panic runtime will always set the `.payload()` of `PanicInfo` to the formatted string. The linked issues show that formatting the message twice can cause problems, so we simply print the already formatted message instead of formatting it again. We can't remove the preformatted payload, because it can be observed by custom panic hooks. fixes rust-lang#110717 fixes rust-itertools/itertools#694 cc `@Amanieu` who broke this in rust-lang#109507
matthiaskrgr
added a commit
to matthiaskrgr/rust
that referenced
this issue
Apr 24, 2023
format panic message only once For `panic!` and friends, the `std` panic runtime will always set the `.payload()` of `PanicInfo` to the formatted string. The linked issues show that formatting the message twice can cause problems, so we simply print the already formatted message instead of formatting it again. We can't remove the preformatted payload, because it can be observed by custom panic hooks. fixes rust-lang#110717 fixes rust-itertools/itertools#694 cc ``@Amanieu`` who broke this in rust-lang#109507
matthiaskrgr
added a commit
to matthiaskrgr/rust
that referenced
this issue
Apr 24, 2023
format panic message only once For `panic!` and friends, the `std` panic runtime will always set the `.payload()` of `PanicInfo` to the formatted string. The linked issues show that formatting the message twice can cause problems, so we simply print the already formatted message instead of formatting it again. We can't remove the preformatted payload, because it can be observed by custom panic hooks. fixes rust-lang#110717 fixes rust-itertools/itertools#694 cc ```@Amanieu``` who broke this in rust-lang#109507
apiraino
removed
the
I-prioritize
Issue: Indicates that prioritization has been requested for this issue.
label
Apr 25, 2023
jyn514
added
A-runtime
Area: std's runtime and "pre-main" init for handling backtraces, unwinds, stack overflows
T-libs
Relevant to the library team, which will review and decide on the PR/issue.
labels
Apr 26, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
A-runtime
Area: std's runtime and "pre-main" init for handling backtraces, unwinds, stack overflows
C-bug
Category: This is a bug.
regression-from-stable-to-nightly
Performance or correctness regression from stable to nightly.
T-libs
Relevant to the library team, which will review and decide on the PR/issue.
Code
I tried this code:
Playground
I expected to see this happen: No panic during runtime
Instead, this happened: Panicked during runtime
Format: was already formatted once
Version it worked on
It most recently worked on: Rust 1.70 (beta) and Rust 1.69 (stable)
Version with regression
rustc --version --verbose
:Backtrace
None
Other
I also reported this here rust-itertools/itertools#694, but I think this one is on
rustc
.@m-ou-se assigning you, because I suspect this has something to do with recent
format_args!
changes.The text was updated successfully, but these errors were encountered: