rust/tests/ui/backtrace, branch beta

Print thread ID in panic message if thread name is unknown

2025-08-06T23:59:47+00:00

`panic!` does not print any identifying information for threads that are unnamed. However, in many cases, the thread ID can be determined. This changes the panic message from something like this: thread '' panicked at src/main.rs:3:5: explicit panic To something like this: thread '' (0xff9bf) panicked at src/main.rs:3:5: explicit panic Stack overflow messages are updated as well. This change applies to both named and unnamed threads. The ID printed is the OS integer thread ID rather than the Rust thread ID, which should also be what debuggers print.

Rollup merge of #144356 - GuillaumeGomez:gcc-ignore-tests, r=jieyouxu

2025-07-26T06:15:08+00:00

Add `ignore-backends` annotations in failing GCC backend ui tests Follow-up of https://github.com/rust-lang/rust/pull/144125. In the GCC backend, we don't support all ui tests yet and we have a list of tests we currently ignore available [here](https://github.com/rust-lang/rustc_codegen_gcc/blob/master/tests/failing-ui-tests.txt). This PR adds the `ignore-backends` annotations to the corresponding ui tests. The second commit is a fix to compiletest, complaining about `ignore-backends`. r? ```@jieyouxu```

Add `ignore-backends` annotations in failing GCC backend ui tests

2025-07-23T11:48:04+00:00

tests: Don't check for self-printed output in std-backtrace.rs test

2025-07-09T06:43:56+00:00

The `Display` implementation for `Backtrace` used to print stack backtrace: but that print was later removed. To make the existing test pass, the print was added to the existing test. But it doesn't make sense to check for something that the test itself does since that will not detect any regressions in the implementation of `Backtrace`. Fully remove the checks.

tests: use `needs-subprocess` instead of `ignore-{wasm32,emscripten,sgx}`

2025-01-23T12:51:29+00:00

Try to write the panic message with a single `write_all` call

2025-01-01T14:58:29+00:00

Run `tests/ui/backtrace/std-backtrace.rs` on MSVC.

2024-12-25T12:44:20+00:00

The original PR which disabled these only mentions them being broken on i686 msvc. Let's try to see if we can reenable this test for msvc (both 32-bit and 64-bit).

Emscripten: Xfail backtrace ui tests

2024-10-16T10:22:14+00:00

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

the output in stderr expects panic-unwind

2024-07-30T06:16:47+00:00

fix interleaved panic output

2024-07-12T15:52:04+00:00

previously, we only held a lock for printing the backtrace itself. since all threads were printing to the same file descriptor, that meant random output in the default panic hook would be interleaved with the backtrace. now, we hold the lock for the full duration of the hook, and the output is ordered.