Tracking issue for wasm32-emscripten ui test failures #131738
Labels
A-testsuite
Area: The testsuite used to check the correctness of rustc
C-bug
Category: This is a bug.
C-tracking-issue
Category: A tracking issue for an RFC or an unstable feature.
O-emscripten
Target: 50% off wasm32-unknown-musl. the savings come out of stdio.h, but hey, you get SDL!
Comments
hoodmane
added a commit
to hoodmane/rust
that referenced
this issue
Oct 16, 2024
It is possible to link libunwind and use the normal backtrace code, but it fails to symbolize stack traces. I investigated and could get the list of instruction pointers and symbol names, but I'm not sure how to use the dwarf info to map from instruction pointer to source location. In any case, fixing this is probably not a high priority. See rust-lang#131738
Urgau
added a commit
to Urgau/rust
that referenced
this issue
Oct 16, 2024
…e-tests, r=jieyouxu Emscripten: Xfail backtrace ui tests It is possible to link libunwind and use the normal backtrace code, but it fails to symbolize stack traces. I investigated and could get the list of instruction pointers and symbol names, but I'm not sure how to use the dwarf info to map from instruction pointer to source location. In any case, fixing this is not a high priority. See rust-lang#131738 r?jieyouxu
matthiaskrgr
added a commit
to matthiaskrgr/rust
that referenced
this issue
Oct 16, 2024
…e-tests, r=jieyouxu Emscripten: Xfail backtrace ui tests It is possible to link libunwind and use the normal backtrace code, but it fails to symbolize stack traces. I investigated and could get the list of instruction pointers and symbol names, but I'm not sure how to use the dwarf info to map from instruction pointer to source location. In any case, fixing this is not a high priority. See rust-lang#131738 r?jieyouxu
rust-timer
added a commit
to rust-lang-ci/rust
that referenced
this issue
Oct 16, 2024
Rollup merge of rust-lang#131776 - hoodmane:emscripten-xfail-backtrace-tests, r=jieyouxu Emscripten: Xfail backtrace ui tests It is possible to link libunwind and use the normal backtrace code, but it fails to symbolize stack traces. I investigated and could get the list of instruction pointers and symbol names, but I'm not sure how to use the dwarf info to map from instruction pointer to source location. In any case, fixing this is not a high priority. See rust-lang#131738 r?jieyouxu
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
These are the tests that are failing after #131705:
abi/numbers-arithmetic/return-float.rs-- adding-Cpanic=abortfixes the failure. The upstream bug report has a C++ reproducer. More reason it would be nice to resolve Support wasm exception handling for Emscripten target #112195.async-await/issue-60709.rs-- Emscripten bug that occurs when-lcand-Ozare passed to the linker, can be reproduced withThe text was updated successfully, but these errors were encountered: