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.

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

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

[AUTO-GENERATED] Migrate ui tests from `//` to `//@` directives

2024-02-16T20:02:50+00:00

Change default panic handler message format.

2023-07-29T09:42:50+00:00

Move /src/test to /tests

2023-01-11T09:32:08+00:00

rust/tests/ui/nll/issue-51345-2.rs, branch master

Print thread ID in panic message if thread name is unknown

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

[AUTO-GENERATED] Migrate ui tests from `//` to `//@` directives

Change default panic handler message format.

Move /src/test to /tests