alexcrichton opened PR #11383 from alexcrichton:force-unwind-tables to bytecodealliance:main:
In #11344 it was found that if Wasmtime had a frame on the stack then an application's previous unwinding was broken. This was due to the fact that Wasmtime's C API artifacts do not have unwind information built-in due to being build with
-Cpanic=abort. This change updates to building the C API artifacts with-Cforce-unwind-tableseven though Rust itself won't use them to assist with embedders that want to unwind. These should in theory be easily strippable if desired and additionally embedders always have the option to build their own version of the C API too.Closes #11344
<!--
Please make sure you include the following information:
If this work has been discussed elsewhere, please include a link to that
conversation. If it was discussed in an issue, just mention "issue #...".Explain why this change is needed. If the details are in an issue already,
this can be brief.Our development process is documented in the Wasmtime book:
https://docs.wasmtime.dev/contributing-development-process.htmlPlease ensure all communication follows the code of conduct:
https://github.com/bytecodealliance/wasmtime/blob/main/CODE_OF_CONDUCT.md
-->
alexcrichton requested wasmtime-default-reviewers for a review on PR #11383.
alexcrichton requested rvolosatovs for a review on PR #11383.
fitzgen submitted PR review.
bjorn3 commented on PR #11383:
By the way https://github.com/rust-lang/rust/pull/143613 will make
-Cforce-unwind-tablesthe default on Linux. It was already force enabled on Windows. macOS would still need-Cforce-unwind-tablesthough.
fitzgen merged PR #11383.
alexcrichton commented on PR #11383:
Oh nice I wasn't aware of that!
Last updated: Dec 06 2025 at 06:05 UTC