about summary refs log tree commit diff
path: root/src/tools/miri/tests/pass/panic/thread_panic.stderr
AgeCommit message (Collapse)AuthorLines
2025-08-06Print thread ID in panic message if thread name is unknownTrevor Gross-2/+2
`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-01-01Try to write the panic message with a single `write_all` callJohn Kåre Alsaker-0/+2
2024-09-16Bump ui testOli Scherer-2/+2
2024-08-24panicking: improve hint for Miri's RUST_BACKTRACE behaviorRalf Jung-1/+1
2024-04-18when suggesting RUST_BACKTRACE=1, add a special note for Miri's env var ↵Ralf Jung-0/+1
isolation
2024-03-03move thread-panic tests to their own file; test getting the thread nameRalf Jung-0/+5