rust/tests/ui/intrinsics/const-eval-select-backtrace-std.run.stderr


thread 'main' ($TID) panicked at $DIR/const-eval-select-backtrace-std.rs:6:8:
byte index 1 is out of bounds of ``
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace
Try to write the panic message with a single `write_all` call 2024-03-15 19:09:24 +01:00
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. 2023-09-11 00:59:31 -04:00			`thread 'main' ($TID) panicked at $DIR/const-eval-select-backtrace-std.rs:6:8:`
Change default panic handler message format. 2023-06-20 19:16:18 +02:00			byte index 1 is out of bounds of ``
Make `const_eval_select` a real intrinsic 2022-08-23 00:07:26 +00:00			note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace