Hood Chatham 476ea45c68 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 probably not a high priority. See https://github.com/rust-lang/rust/issues/131738		2024-10-16 12:22:14 +02:00
..
auxiliary	Move 100 entries from tests/ui into subdirs	2024-05-20 19:55:59 -07:00
apple-no-dsymutil.rs	Make more of the test suite run on Mac Catalyst	2024-05-28 12:31:33 +02:00
backtrace.rs	Move 100 entries from tests/ui into subdirs	2024-05-20 19:55:59 -07:00
dylib-dep.rs	Emscripten: Xfail backtrace ui tests	2024-10-16 12:22:14 +02:00
line-tables-only.rs	Emscripten: Xfail backtrace ui tests	2024-10-16 12:22:14 +02:00
std-backtrace.rs	Move 100 entries from tests/ui into subdirs	2024-05-20 19:55:59 -07:00
synchronized-panic-handler.rs	the output in stderr expects panic-unwind	2024-07-30 08:16:47 +02:00
synchronized-panic-handler.run.stderr	the output in stderr expects panic-unwind	2024-07-30 08:16:47 +02:00