rust/src/tools/miri/tests/panic/function_calls, branch perf-tmp

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.

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

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

Bump ui test

2024-09-16T21:05:42+00:00

panicking: improve hint for Miri's RUST_BACKTRACE behavior

2024-08-24T12:38:50+00:00

Remove c_unwind from tests and fix tests

2024-06-19T12:54:55+00:00

when suggesting RUST_BACKTRACE=1, add a special note for Miri's env var isolation

2024-04-18T10:05:08+00:00

Change default panic handler message format.

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

Add 'src/tools/miri/' from commit '75dd959a3a40eb5b4574f8d2e23aa6efbeb33573'

2022-09-21T15:36:26+00:00

git-subtree-dir: src/tools/miri git-subtree-mainline: 3f3167fb59341ac3240ca1774f48e8c053219131 git-subtree-split: 75dd959a3a40eb5b4574f8d2e23aa6efbeb33573