Trevor Gross 289fe36d37 Print thread ID in panic message if thread name is unknown ... `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 '<unnamed>' panicked at src/main.rs:3:5: explicit panic To something like this: thread '<unnamed>' (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.		2025-08-06 23:59:47 +00: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	tests: use needs-subprocess instead of ignore-{wasm32,emscripten,sgx}	2025-01-23 20:51:29 +08:00
dylib-dep.rs	Add ignore-backends annotations in failing GCC backend ui tests	2025-07-23 13:48:04 +02:00
line-tables-only.rs	Emscripten: Xfail backtrace ui tests	2024-10-16 12:22:14 +02:00
std-backtrace.rs	tests: Don't check for self-printed output in std-backtrace.rs test	2025-07-09 08:43:56 +02: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	Print thread ID in panic message if thread name is unknown	2025-08-06 23:59:47 +00:00