Skip to content

Commit

Permalink
Emscripten: Xfail backtrace ui tests
Browse files Browse the repository at this point in the history
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
  • Loading branch information
hoodmane committed Oct 16, 2024
1 parent 9618da7 commit 476ea45
Show file tree
Hide file tree
Showing 2 changed files with 2 additions and 0 deletions.
1 change: 1 addition & 0 deletions tests/ui/backtrace/dylib-dep.rs
Original file line number Diff line number Diff line change
Expand Up @@ -9,6 +9,7 @@
//@ ignore-musl musl doesn't support dynamic libraries (at least when the original test was written).
//@ needs-unwind
//@ compile-flags: -g -Copt-level=0 -Cstrip=none -Cforce-frame-pointers=yes
//@ ignore-emscripten Requires custom symbolization code
//@ aux-crate: dylib_dep_helper=dylib-dep-helper.rs
//@ aux-crate: auxiliary=dylib-dep-helper-aux.rs
//@ run-pass
Expand Down
1 change: 1 addition & 0 deletions tests/ui/backtrace/line-tables-only.rs
Original file line number Diff line number Diff line change
Expand Up @@ -10,6 +10,7 @@
//@ compile-flags: -Cstrip=none -Cdebuginfo=line-tables-only
//@ ignore-android FIXME #17520
//@ ignore-fuchsia Backtraces not symbolized
//@ ignore-emscripten Requires custom symbolization code
//@ needs-unwind
//@ aux-build: line-tables-only-helper.rs

Expand Down

0 comments on commit 476ea45

Please sign in to comment.