Skip to content

Set no-op backtrace for all wasm family targets#756

Open
arjunr2 wants to merge 1 commit into
rust-lang:masterfrom
arjunr2:master
Open

Set no-op backtrace for all wasm family targets#756
arjunr2 wants to merge 1 commit into
rust-lang:masterfrom
arjunr2:master

Conversation

@arjunr2

@arjunr2 arjunr2 commented Apr 23, 2026

Copy link
Copy Markdown

Particularly needed to support wasm32-wali-linux-musl appropriately

@workingjubilee

Copy link
Copy Markdown
Member

it is not clear to me that backtraces should be no-op for all wasm-family targets|

@arjunr2

arjunr2 commented May 31, 2026

Copy link
Copy Markdown
Author

Backtraces aren't supported on any wasm target besides those that use emscripten right now; I figured this should be reflected. Would you rather I gate it on just not(all(target_arch = wasm32, target_os = linux))?

@workingjubilee

Copy link
Copy Markdown
Member

My understanding, and it could be wrong, is the current environs is that one or two wasm targets are moving towards unwinding support, where it seems better to have noisier failures when they try to build and this code starts mattering than a silent failure to produce traces.

And that everyone else who isn't, is just building with panic="abort" so it doesn't matter to them?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants