| Age | Commit message (Collapse) | Author | Lines | |
|---|---|---|---|---|
| 2025-08-06 | Print thread ID in panic message if thread name is unknown | Trevor Gross | -3/+3 | |
| `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-01 | Try to write the panic message with a single `write_all` call | John Kåre Alsaker | -0/+3 | |
| 2024-09-16 | Bump ui test | Oli Scherer | -3/+3 | |
| 2024-08-24 | panicking: improve hint for Miri's RUST_BACKTRACE behavior | Ralf Jung | -1/+1 | |
| 2024-06-19 | Remove c_unwind from tests and fix tests | Gary Guo | -1/+1 | |
| 2024-04-18 | when suggesting RUST_BACKTRACE=1, add a special note for Miri's env var ↵ | Ralf Jung | -0/+1 | |
| isolation | ||||
| 2023-07-29 | Change default panic handler message format. | Mara Bos | -3/+6 | |
| 2022-09-21 | Add 'src/tools/miri/' from commit '75dd959a3a40eb5b4574f8d2e23aa6efbeb33573' | Oli Scherer | -0/+42 | |
| git-subtree-dir: src/tools/miri git-subtree-mainline: 3f3167fb59341ac3240ca1774f48e8c053219131 git-subtree-split: 75dd959a3a40eb5b4574f8d2e23aa6efbeb33573 | ||||
