6 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
Ralf Jung	c4cab8a15c	bless tests for changed library path	2024-11-30 11:22:52 +01:00
bjorn3	feeeb5c48e	Bless tests	2024-08-02 11:34:54 +00:00
Mara Bos	4017c5c945	Fix tests.	2023-07-29 11:47:26 +02:00
Martin Nordholts	075a6bbef9	Regression test println!() panic message on ErrorKind::BrokenPipe ... No existing test failed if the [`panic!()`][1] of the `println!()` family of functions was removed, or if its message was changed. So add such a test. [1] 104f4300cf/library/std/src/io/stdio.rs (L1007-L1009)	2023-07-26 13:41:39 +02:00