rust/tests/ui/mir/lint
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
..
assignment-overlap.rs compiletest: Support matching on non-json lines in compiler output 2025-05-04 18:27:45 +03:00
call-overlap.rs compiletest: Support matching on non-json lines in compiler output 2025-05-04 18:27:45 +03:00
no-storage.rs compiletest: Require //~ annotations even if error-pattern is specified 2025-04-03 11:08:55 +03:00
storage-live.rs Print thread ID in panic message if thread name is unknown 2025-08-06 23:59:47 +00:00
storage-live.stderr compiletest: Support matching on non-json lines in compiler output 2025-05-04 18:27:45 +03:00
storage-return.rs compiletest: Support matching on non-json lines in compiler output 2025-05-04 18:27:45 +03:00