| Age | Commit message (Collapse) | Author | Lines | |
|---|---|---|---|---|
| 2025-08-06 | Print thread ID in panic message if thread name is unknown | Trevor Gross | -1/+1 | |
| `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-07-19 | Give a message with a span on validation error | Scott McMurray | -4/+10 | |
| 2025-01-01 | Try to write the panic message with a single `write_all` call | John Kåre Alsaker | -0/+1 | |
| 2024-05-27 | MIR validation: ensure that downcast projection is followed by field projection | Ralf Jung | -1/+1 | |
| 2024-05-24 | miri: receive the blessings of validate.rs | Jubilee Young | -1/+1 | |
| 2024-04-19 | make test not leak rustc crate hash | Ralf Jung | -1/+1 | |
| 2024-04-18 | add test checking that we do run MIR validation | Ralf Jung | -0/+21 | |
