5 Commits

Author	SHA1	Message	Date
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
John Kåre Alsaker	4bf85c25ec	Try to write the panic message with a single write_all call	2025-01-01 15:58:29 +01:00
Zalathar	c4aa7a71a9	Port run-make/libtest-json to rmake	2024-08-13 13:27:15 +10:00
Mara Bos	0e729404da	Change default panic handler message format.	2023-07-29 11:42:50 +02:00
Joshua Nelson	433da1fc04	Move almost all run-make-fulldeps to run-make ... They pass fine.	2023-03-30 07:34:55 -05:00