Fix backtraces with `-C panic=abort` on linux; emit unwind tables by default #143613

Enselic · 2025-07-07T20:56:59Z

The linux backtrace unwinder relies on unwind tables to work properly, and generating and printing a backtrace is done by for example the default panic hook.

Begin emitting unwind tables by default again with -C panic=abort (see history below) so that backtraces work.

Closes #81902 which is regression-from-stable-to-stable
Closes #94815

History

Backtraces with -C panic=abort used to work in Rust 1.22 but broke in Rust 1.23, because in 1.23 we stopped emitting unwind tables with -C panic=abort (see #45031 and #81902 (comment)).

In 1.45 a workaround in the form of -C force-unwind-tables=yes was added (see #69984).

-C panic=abort was added in Rust 1.10 and the motivation was binary size and compile time. But given how confusing that behavior has turned out to be, it is better to make binary size optimization opt-in with -C force-unwind-tables=no rather than default since the current default breaks backtraces.

Besides, if binary size is a primary concern, there are many other tricks that can be used that has a higher impact.

Release Note Entry Draft:

Compatibility Notes

Fix backtraces with -C panic=abort on Linux by generating unwind tables by default. Build with -C force-unwind-tables=no to keep omitting unwind tables.

try-job: aarch64-apple
try-job: armhf-gnu
try-job: aarch64-msvc-1

rustbot · 2025-07-07T20:57:04Z

r? @petrochenkov

rustbot has assigned @petrochenkov.
They will have a look at your PR within the next two weeks and either review your PR or reassign to another reviewer.

Use r? to explicitly pick a reviewer

rustbot · 2025-07-07T20:57:06Z

These commits modify compiler targets.
(See the Target Tier Policy.)

This PR modifies run-make tests.

cc @jieyouxu

compiler/rustc_session/src/session.rs

hanna-kruppe · 2025-07-07T21:11:39Z

Note that it’s currently pretty tricky to change this setting from whatever the default is on a given target, since there’s no Cargo profile setting for it (unlike the panic strategy), cc rust-lang/cargo#15333

This observation can probably be used as argument for or against this change.

bjorn3 · 2025-07-07T21:36:02Z

If you don't want unwind tables to save space you probably want to strip it out after linking anyway. -Cpanic=abort still gives unwind tables for the standard library on targets supporting panic=unwind unless -Zbuild-std is used. Would be a good idea to document this stripping in the min-sized-rust guide. You have to strip .eh_frame, .eh_frame_hdr and .gcc_except_table. One complication however is that we do have to keep unwind tables for functions that call extern "C-unwind" functions for soundness though.

hanna-kruppe · 2025-07-07T22:04:17Z

If there's a way to drop all unwind tables that can safely be dropped but no more, then that would be a nice new feature (-Cstrip variant?) or addition to min-sized-rust. But if you're going all out on minimizing binary size, then you'll already want -Zbuild-std for a dozen other reasons anyway. I mostly brought it up from the POV of: if the default is changed, how easily can an ordinary user of stable Rust get back to the current behavior?

Enselic · 2025-07-08T14:48:26Z

Changes since the initial version d113be9:

Add a regression test specifically for backtrace with -C panic=abort.
Adjust tests/run-make/panic-abort-eh_frame/rmake.rs. I will also ping the people that added it in Prevent .eh_frame from being emitted for -C panic=abort #112403 for review. Edit: Done.
I added a draft release note entry to the PR description.

if the default is changed, how easily can an ordinary user of stable Rust get back to the current behavior?

I don't think ordinary users want to go back to the regression introduced in Rust 1.23, because I expect ordinary users to want backtraces to work.

For advanced users I don't think it's too much to ask to require building with -C force-unwind-tables=no to opt back in to the current (arguably broken) behavior.

nbdd0121 · 2025-07-08T15:49:48Z

If you don't want unwind tables to save space you probably want to strip it out after linking anyway.

Stripping unwind tables is going to change the behaviour if you link in some foreign static library (e.g. a C++ library) that depends on unwinding.

One complication however is that we do have to keep unwind tables for functions that call extern "C-unwind" functions for soundness though.

I think there is no soundness concern, it's just correctness? Unwinding will stop with error if it cannot find unwind tables.

tests/run-make/panic-abort-eh_frame/rmake.rs

bjorn3 · 2025-07-09T08:48:57Z

I think there is no soundness concern, it's just correctness? Unwinding will stop with error if it cannot find unwind tables.

Right, only keeping .eh_frame without the LSDA would cause soundness issues I think.

petrochenkov · 2025-07-14T16:47:08Z

The implementation LGTM, but is there some consensus about doing this?
I haven't heard from the "we should keep minimizing size" camp yet.

petrochenkov · 2025-07-14T16:48:19Z

Let's start a compiler FCP, see the PR description for what is changed.
@rfcbot merge

rfcbot · 2025-07-14T16:48:21Z

nagisa · 2025-07-14T21:28:57Z

I'm +1 on this change if for no other reason that my personal use-cases generally tend to prefer -Cpanic=abort for perf/compile time reasons, but I also almost always care a bunch about keeping unwind tables for stack traces for profiling and just generally.

AT least my experience suggests it to be a more common use-case to want these working out of the box which is a good argument to making it work by default. Another is that people pursuing minimum binary size tend to have to apply modifications to how they build anyway, so another flag/step doesn't sound like too onerous a problem (so long as we figure out how to strip only those uwtables that don't affect soundness.)

Noratrieb · 2025-07-31T19:05:28Z

@rfcbot reviewed

Not a blocking concern, but it would be nice if the documentation was made more precise about which targets have which behavior: https://doc.rust-lang.org/nightly/rustc/codegen-options/index.html?highlight=unwind-tables#force-unwind-tables

Enselic · 2025-10-02T19:31:36Z

@bors2 try

Fix backtraces with `-C panic=abort` on linux; emit unwind tables by default try-job: aarch64-apple try-job: armhf-gnu try-job: aarch64-msvc-1

rust-bors · 2025-10-02T22:06:58Z

☀️ Try build successful (CI)
Build commit: 4c5d411 (4c5d411e208017c395b19b02008351c99080943d, parent: 5c7ae0c7ed184c603e5224604a9f33ca0e8e0b36)

Enselic · 2025-10-03T06:32:25Z

@petrochenkov Ready for r+ if this diff looks ok.

@rustbot ready

petrochenkov · 2025-10-03T12:35:05Z

@bors r+

bors · 2025-10-03T12:35:09Z

📌 Commit fe66eaa has been approved by petrochenkov

It is now in the queue for this repository.

bors · 2025-10-03T15:02:40Z

⌛ Testing commit fe66eaa with merge f437c86...

bors · 2025-10-03T18:14:34Z

☀️ Test successful - checks-actions
Approved by: petrochenkov
Pushing f437c86 to master...

github-actions · 2025-10-03T18:17:32Z

What is this?

This is an experimental post-merge analysis report that shows differences in test outcomes between the merged PR and its parent PR.

Comparing 8b6b15b (parent) -> f437c86 (this PR)

Test differences

Show 7 test diffs

Stage 1

[ui] tests/ui/panics/panic-abort-backtrace-without-debuginfo.rs: [missing] -> pass (J1)

Stage 2

[ui] tests/ui/panics/panic-abort-backtrace-without-debuginfo.rs: [missing] -> pass (J0)
[ui] tests/ui/panics/panic-abort-backtrace-without-debuginfo.rs: [missing] -> ignore (ignored when the target is arm-unknown-linux-gnueabihf (FIXME(undefined reference to __aeabi_unwind_cpp_pr0 on arm-unknown-linux-gnueabihf with no_std and -Cforce-unwind-tables=yes #146996) Try removing this once undefined reference to __aeabi_unwind_cpp_pr0 on arm-unknown-linux-gnueabihf with no_std and -Cforce-unwind-tables=yes #146996 has been fixed.)) (J2)
[ui] tests/ui/panics/panic-abort-backtrace-without-debuginfo.rs: [missing] -> ignore (ignored when the target environment is msvc (Backtraces on Windows requires debuginfo which we can't use here)) (J3)
[ui] tests/ui/panics/panic-abort-backtrace-without-debuginfo.rs: [missing] -> ignore (ignored when the target vendor is Apple) (J4)

Additionally, 2 doctest diffs were found. These are ignored, as they are noisy.

Job group index

J0: aarch64-gnu, aarch64-gnu-llvm-20-1, arm-android, dist-i586-gnu-i586-i686-musl, i686-gnu-1, i686-gnu-nopt-1, test-various, x86_64-gnu, x86_64-gnu-debug, x86_64-gnu-llvm-20, x86_64-gnu-llvm-20-2, x86_64-gnu-nopt, x86_64-gnu-stable, x86_64-mingw-1
J1: x86_64-gnu-llvm-20-3
J2: armhf-gnu
J3: aarch64-msvc-1, i686-msvc-1, x86_64-msvc-1
J4: aarch64-apple

Test dashboard

Run

cargo run --manifest-path src/ci/citool/Cargo.toml -- \
    test-dashboard f437c86ef829e43c6aa27641f53040a999a092af --output-dir test-dashboard

And then open test-dashboard/index.html in your browser to see an overview of all executed tests.

Job duration changes

pr-check-1: 1431.8s -> 1849.5s (29.2%)
i686-gnu-1: 7144.0s -> 8216.9s (15.0%)
aarch64-gnu-llvm-20-1: 3404.2s -> 3879.3s (14.0%)
dist-x86_64-apple: 7979.0s -> 6921.2s (-13.3%)
x86_64-rust-for-linux: 2690.2s -> 3013.7s (12.0%)
i686-gnu-2: 5538.8s -> 6162.0s (11.3%)
i686-gnu-nopt-1: 7366.7s -> 8192.0s (11.2%)
aarch64-msvc-2: 5298.1s -> 4803.8s (-9.3%)
dist-apple-various: 3264.0s -> 3566.4s (9.3%)
x86_64-gnu-debug: 6584.2s -> 7193.7s (9.3%)

How to interpret the job duration changes?

Job durations can vary a lot, based on the actual runner instance
that executed the job, system noise, invalidated caches, etc. The table above is provided
mostly for t-infra members, for simpler debugging of potential CI slow-downs.

rust-timer · 2025-10-03T19:25:47Z

Finished benchmarking commit (f437c86): comparison URL.

Overall result: ✅ improvements - no action needed

@rustbot label: -perf-regression

Instruction count

Our most reliable metric. Used to determine the overall result above. However, even this metric can be noisy.

	mean	range	count
Regressions ❌ (primary)	-	-	0
Regressions ❌ (secondary)	-	-	0
Improvements ✅ (primary)	-	-	0
Improvements ✅ (secondary)	-0.5%	[-0.5%, -0.5%]	2
All ❌✅ (primary)	-	-	0

Max RSS (memory usage)

Results (primary -5.8%, secondary -0.6%)

A less reliable metric. May be of interest, but not used to determine the overall result above.

	mean	range	count
Regressions ❌ (primary)	-	-	0
Regressions ❌ (secondary)	0.5%	[0.4%, 0.5%]	3
Improvements ✅ (primary)	-5.8%	[-5.8%, -5.8%]	1
Improvements ✅ (secondary)	-2.2%	[-2.5%, -2.0%]	2
All ❌✅ (primary)	-5.8%	[-5.8%, -5.8%]	1

Cycles

Results (secondary 0.7%)

A less reliable metric. May be of interest, but not used to determine the overall result above.

	mean	range	count
Regressions ❌ (primary)	-	-	0
Regressions ❌ (secondary)	3.6%	[3.3%, 4.0%]	2
Improvements ✅ (primary)	-	-	0
Improvements ✅ (secondary)	-2.2%	[-2.2%, -2.1%]	2
All ❌✅ (primary)	-	-	0

Binary size

This benchmark run did not return any relevant results for this metric.

Bootstrap: 471.778s -> 472.633s (0.18%)
Artifact size: 388.26 MiB -> 388.27 MiB (0.00%)

Fix backtraces with `-C panic=abort` on linux; emit unwind tables by default The linux backtrace unwinder relies on unwind tables to work properly, and generating and printing a backtrace is done by for example the default panic hook. Begin emitting unwind tables by default again with `-C panic=abort` (see history below) so that backtraces work. Closes rust-lang/rust#81902 which is **regression-from-stable-to-stable** Closes rust-lang/rust#94815 ### History Backtraces with `-C panic=abort` used to work in Rust 1.22 but broke in Rust 1.23, because in 1.23 we stopped emitting unwind tables with `-C panic=abort` (see rust-lang/rust#45031 and rust-lang/rust#81902 (comment)). In 1.45 a workaround in the form of `-C force-unwind-tables=yes` was added (see rust-lang/rust#69984). `-C panic=abort` was added in [Rust 1.10](https://blog.rust-lang.org/2016/07/07/Rust-1.10/#what-s-in-1-10-stable) and the motivation was binary size and compile time. But given how confusing that behavior has turned out to be, it is better to make binary size optimization opt-in with `-C force-unwind-tables=no` rather than default since the current default breaks backtraces. Besides, if binary size is a primary concern, there are many other tricks that can be used that has a higher impact. # Release Note Entry Draft: ## Compatibility Notes * [Fix backtraces with `-C panic=abort` on Linux by generating unwind tables by default](rust-lang/rust#143613). Build with `-C force-unwind-tables=no` to keep omitting unwind tables. try-job: aarch64-apple try-job: armhf-gnu try-job: aarch64-msvc-1

…tables-qnx, r=wesleywiser Fix backtraces with `-C panic=abort` on qnx; emit unwind tables by default While syncing rust-lang#143613 into Ferrocene as part of ferrocene/ferrocene#1803, we noted a failure on our QNX targets: ``` ---- [ui] tests/ui/panics/panic-abort-backtrace-without-debuginfo.rs stdout ---- error: test did not exit with success! code=Some(134) so test would pass with `run-crash` status: exit status: 134 command: RUSTC="/home/ci/project/build/x86_64-unknown-linux-gnu/stage2/bin/rustc" RUST_TEST_THREADS="1" "/home/ci/project/build/x86_64-unknown-linux-gnu/stage1-tools-bin/remote-test-client" "run" "0" "/home/ci/project/build/x86_64-unknown-linux-gnu/test/ui/panics/panic-abort-backtrace-without-debuginfo/a" --- stdout ------------------------------- uploaded "/home/ci/project/build/x86_64-unknown-linux-gnu/test/ui/panics/panic-abort-backtrace-without-debuginfo/a", waiting for result died due to signal 6 ------------------------------------------ --- stderr ------------------------------- thread 'main' (1) panicked at /home/ci/project/tests/ui/panics/panic-abort-backtrace-without-debuginfo.rs:39:9: ERROR: no `this_function_must_be_in_the_backtrace` in stderr! actual stderr: thread 'main' (1) panicked at /home/ci/project/tests/ui/panics/panic-abort-backtrace-without-debuginfo.rs:27:5: generate panic backtrace stack backtrace: 0: 0x4e66a53643 - <std::sys::backtrace::BacktraceLock::print::DisplayBacktrace as core::fmt::Display>::fmt::h55e010263b1e3169 1: 0x4e66a68cd2 - core::fmt::write::h0d6e2e8752abc333 2: 0x4e66a16919 - std::io::Write::write_fmt::h71c4c024d832b384 3: 0x4e66a1f8e2 - std::sys::backtrace::BacktraceLock::print::hdd80dfdf90bb7100 4: 0x4e66a221e0 - std::panicking::default_hook::{{closure}}::h77758f25a686500f 5: 0x4e66a21f69 - std::panicking::default_hook::ha63f7d476af6c267 6: 0x4e66a22999 - std::panicking::panic_with_hook::h3a36a8a0f0dd8ccd 7: 0x4e66a21cac - std::panicking::begin_panic::{{closure}}::h570dedb92e232392 8: 0x4e66a1fa69 - std::sys::backtrace::__rust_end_short_backtrace::h5366eec354f92733 9: 0x4e669f9589 - std::panicking::begin_panic::h04a4bd4c33dd4056 10: 0x4e66a00aca - panic_abort_backtrace_without_debuginfo::and_this_function_too::h5b034b94cbe9c3d3 note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace ------------------------------------------ ---- [ui] tests/ui/panics/panic-abort-backtrace-without-debuginfo.rs stdout end ---- failures: [ui] tests/ui/panics/panic-abort-backtrace-without-debuginfo.rs test result: FAILED. 19958 passed; 1 failed; 328 ignored; 0 measured; 0 filtered out; finished in 1827.71s Some tests failed in compiletest suite=ui mode=ui host=x86_64-unknown-linux-gnu target=x86_64-pc-nto-qnx710 Build completed unsuccessfully in 0:43:28 Exited with code exit status 1 ``` This patch applies the same fix as the one found in rust-lang#143613 of adding the `default_uwtable: true` to the target. I've run it locally, when ferrocene/ferrocene#1803 merges we'll know it has passed within our CI, which is about a close an analog as I can offer to Rust.

Rollup merge of #147454 - ferrocene:hoverbear/panic-abort-uwtables-qnx, r=wesleywiser Fix backtraces with `-C panic=abort` on qnx; emit unwind tables by default While syncing #143613 into Ferrocene as part of ferrocene/ferrocene#1803, we noted a failure on our QNX targets: ``` ---- [ui] tests/ui/panics/panic-abort-backtrace-without-debuginfo.rs stdout ---- error: test did not exit with success! code=Some(134) so test would pass with `run-crash` status: exit status: 134 command: RUSTC="/home/ci/project/build/x86_64-unknown-linux-gnu/stage2/bin/rustc" RUST_TEST_THREADS="1" "/home/ci/project/build/x86_64-unknown-linux-gnu/stage1-tools-bin/remote-test-client" "run" "0" "/home/ci/project/build/x86_64-unknown-linux-gnu/test/ui/panics/panic-abort-backtrace-without-debuginfo/a" --- stdout ------------------------------- uploaded "/home/ci/project/build/x86_64-unknown-linux-gnu/test/ui/panics/panic-abort-backtrace-without-debuginfo/a", waiting for result died due to signal 6 ------------------------------------------ --- stderr ------------------------------- thread 'main' (1) panicked at /home/ci/project/tests/ui/panics/panic-abort-backtrace-without-debuginfo.rs:39:9: ERROR: no `this_function_must_be_in_the_backtrace` in stderr! actual stderr: thread 'main' (1) panicked at /home/ci/project/tests/ui/panics/panic-abort-backtrace-without-debuginfo.rs:27:5: generate panic backtrace stack backtrace: 0: 0x4e66a53643 - <std::sys::backtrace::BacktraceLock::print::DisplayBacktrace as core::fmt::Display>::fmt::h55e010263b1e3169 1: 0x4e66a68cd2 - core::fmt::write::h0d6e2e8752abc333 2: 0x4e66a16919 - std::io::Write::write_fmt::h71c4c024d832b384 3: 0x4e66a1f8e2 - std::sys::backtrace::BacktraceLock::print::hdd80dfdf90bb7100 4: 0x4e66a221e0 - std::panicking::default_hook::{{closure}}::h77758f25a686500f 5: 0x4e66a21f69 - std::panicking::default_hook::ha63f7d476af6c267 6: 0x4e66a22999 - std::panicking::panic_with_hook::h3a36a8a0f0dd8ccd 7: 0x4e66a21cac - std::panicking::begin_panic::{{closure}}::h570dedb92e232392 8: 0x4e66a1fa69 - std::sys::backtrace::__rust_end_short_backtrace::h5366eec354f92733 9: 0x4e669f9589 - std::panicking::begin_panic::h04a4bd4c33dd4056 10: 0x4e66a00aca - panic_abort_backtrace_without_debuginfo::and_this_function_too::h5b034b94cbe9c3d3 note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace ------------------------------------------ ---- [ui] tests/ui/panics/panic-abort-backtrace-without-debuginfo.rs stdout end ---- failures: [ui] tests/ui/panics/panic-abort-backtrace-without-debuginfo.rs test result: FAILED. 19958 passed; 1 failed; 328 ignored; 0 measured; 0 filtered out; finished in 1827.71s Some tests failed in compiletest suite=ui mode=ui host=x86_64-unknown-linux-gnu target=x86_64-pc-nto-qnx710 Build completed unsuccessfully in 0:43:28 Exited with code exit status 1 ``` This patch applies the same fix as the one found in #143613 of adding the `default_uwtable: true` to the target. I've run it locally, when ferrocene/ferrocene#1803 merges we'll know it has passed within our CI, which is about a close an analog as I can offer to Rust.

Fix backtraces with `-C panic=abort` on linux; emit unwind tables by default The linux backtrace unwinder relies on unwind tables to work properly, and generating and printing a backtrace is done by for example the default panic hook. Begin emitting unwind tables by default again with `-C panic=abort` (see history below) so that backtraces work. Closes rust-lang/rust#81902 which is **regression-from-stable-to-stable** Closes rust-lang/rust#94815 ### History Backtraces with `-C panic=abort` used to work in Rust 1.22 but broke in Rust 1.23, because in 1.23 we stopped emitting unwind tables with `-C panic=abort` (see rust-lang/rust#45031 and rust-lang/rust#81902 (comment)). In 1.45 a workaround in the form of `-C force-unwind-tables=yes` was added (see rust-lang/rust#69984). `-C panic=abort` was added in [Rust 1.10](https://blog.rust-lang.org/2016/07/07/Rust-1.10/#what-s-in-1-10-stable) and the motivation was binary size and compile time. But given how confusing that behavior has turned out to be, it is better to make binary size optimization opt-in with `-C force-unwind-tables=no` rather than default since the current default breaks backtraces. Besides, if binary size is a primary concern, there are many other tricks that can be used that has a higher impact. # Release Note Entry Draft: ## Compatibility Notes * [Fix backtraces with `-C panic=abort` on Linux by generating unwind tables by default](rust-lang/rust#143613). Build with `-C force-unwind-tables=no` to keep omitting unwind tables. try-job: aarch64-apple try-job: armhf-gnu try-job: aarch64-msvc-1

rustbot assigned petrochenkov Jul 7, 2025

rustbot added A-run-make Area: port run-make Makefiles to rmake.rs S-waiting-on-review Status: Awaiting review from the assignee but also interested parties. T-compiler Relevant to the compiler team, which will review and decide on the PR/issue. labels Jul 7, 2025

This was referenced Jul 7, 2025

RUST_BACKTRACE truncated with -Cpanic=abort #81902

Closed

Please default "force-unwind-tables" to "yes" on Linux, so that unwind tables are present even if panic = "abort" #94815

Closed

bjorn3 reviewed Jul 7, 2025

View reviewed changes

compiler/rustc_session/src/session.rs Outdated Show resolved Hide resolved

Enselic changed the title ~~Emit unwind tables by default with -Cpanic=abort on linux~~ Fix backtraces with -C panic=abort on linux; emit unwind tables by default Jul 7, 2025

Enselic force-pushed the panic-abort-uwtables branch from d113be9 to 826aa60 Compare July 8, 2025 14:47

Enselic mentioned this pull request Jul 8, 2025

Prevent .eh_frame from being emitted for -C panic=abort #112403

Merged

nbdd0121 reviewed Jul 8, 2025

View reviewed changes

tests/run-make/panic-abort-eh_frame/rmake.rs Show resolved Hide resolved

rfcbot added proposed-final-comment-period Proposed to merge/close by relevant subteam, see T-<team> label. Will enter FCP once signed off. disposition-merge This issue / PR is in PFCP or FCP with a disposition to merge it. labels Jul 14, 2025

petrochenkov added S-waiting-on-team DEPRECATED: Use the team-based variants `S-waiting-on-t-lang`, `S-waiting-on-t-compiler`, ... and removed S-waiting-on-review Status: Awaiting review from the assignee but also interested parties. labels Jul 14, 2025

bjorn3 mentioned this pull request Aug 6, 2025

Build C API release artifacts with unwind tables bytecodealliance/wasmtime#11383

Merged

This comment was marked as resolved.

Sign in to view

Enselic force-pushed the panic-abort-uwtables branch from 603ae9f to fe66eaa Compare October 2, 2025 17:49

This comment has been minimized.

Sign in to view

rust-bors bot added a commit that referenced this pull request Oct 2, 2025

Auto merge of #143613 - Enselic:panic-abort-uwtables, r=<try>

4c5d411

Fix backtraces with `-C panic=abort` on linux; emit unwind tables by default try-job: aarch64-apple try-job: armhf-gnu try-job: aarch64-msvc-1

rustbot added S-waiting-on-review Status: Awaiting review from the assignee but also interested parties. and removed S-waiting-on-author Status: This is awaiting some action (such as code changes or more information) from the author. labels Oct 3, 2025

bors added S-waiting-on-bors Status: Waiting on bors to run and complete tests. Bors will change the label on completion. and removed S-waiting-on-review Status: Awaiting review from the assignee but also interested parties. labels Oct 3, 2025

bors added the merged-by-bors This PR was explicitly merged by bors. label Oct 3, 2025

bors merged commit f437c86 into rust-lang:master Oct 3, 2025
12 checks passed

rustbot added this to the 1.92.0 milestone Oct 3, 2025

stevemk14ebr mentioned this pull request Oct 3, 2025

force-unwind-tables has no effect on windows #85582

Open

Hoverbear mentioned this pull request Oct 7, 2025

Fix backtraces with -C panic=abort on qnx; emit unwind tables by default #147454

Merged

Fix backtraces with -C panic=abort on linux; emit unwind tables by default #143613

Fix backtraces with -C panic=abort on linux; emit unwind tables by default #143613

Uh oh!

Conversation

Enselic commented Jul 7, 2025 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

History

Release Note Entry Draft:

Compatibility Notes

Uh oh!

rustbot commented Jul 7, 2025

Uh oh!

rustbot commented Jul 7, 2025

Uh oh!

Uh oh!

hanna-kruppe commented Jul 7, 2025

Uh oh!

bjorn3 commented Jul 7, 2025

Uh oh!

hanna-kruppe commented Jul 7, 2025

Uh oh!

Enselic commented Jul 8, 2025 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

nbdd0121 commented Jul 8, 2025

Uh oh!

Uh oh!

bjorn3 commented Jul 9, 2025

Uh oh!

petrochenkov commented Jul 14, 2025

Uh oh!

petrochenkov commented Jul 14, 2025

Uh oh!

rfcbot commented Jul 14, 2025 • edited by spastorino Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

nagisa commented Jul 14, 2025

Uh oh!

Noratrieb commented Jul 31, 2025

Uh oh!

This comment was marked as resolved.

Enselic commented Oct 2, 2025

Uh oh!

This comment has been minimized.

rust-bors bot commented Oct 2, 2025

Uh oh!

Enselic commented Oct 3, 2025

Uh oh!

petrochenkov commented Oct 3, 2025

Uh oh!

bors commented Oct 3, 2025

Uh oh!

bors commented Oct 3, 2025

Uh oh!

bors commented Oct 3, 2025

Uh oh!

Uh oh!

github-actions bot commented Oct 3, 2025

Test differences

Stage 1

Stage 2

Job duration changes

Uh oh!

rust-timer commented Oct 3, 2025

Overall result: ✅ improvements - no action needed

Instruction count

Max RSS (memory usage)

Cycles

Binary size

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

18 participants

Fix backtraces with `-C panic=abort` on linux; emit unwind tables by default #143613

Fix backtraces with `-C panic=abort` on linux; emit unwind tables by default #143613

Enselic commented Jul 7, 2025 •

edited

Loading

Enselic commented Jul 8, 2025 •

edited

Loading

rfcbot commented Jul 14, 2025 •

edited by spastorino

Loading