rust - https://github.com/rust-lang/rust

Age	Commit message (Collapse)	Author	Lines
2025-09-26	Ignore more failing ui tests for GCC backend	Guillaume Gomez	-2/+2

2025-08-06	Print thread ID in panic message if thread name is unknown	Trevor Gross	-2/+2
	`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-01-01	Try to write the panic message with a single `write_all` call	John Kåre Alsaker	-0/+2

2024-07-30	the output in stderr expects panic-unwind	aissata	-2/+2

2024-07-12	fix interleaved panic output	jyn	-4/+4
	previously, we only held a lock for printing the backtrace itself. since all threads were printing to the same file descriptor, that meant random output in the default panic hook would be interleaved with the backtrace. now, we hold the lock for the full duration of the hook, and the output is ordered.
2024-07-05	add test that multi-threaded panics aren't interleaved	jyn	-0/+5