289fe36d37
`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.
34 lines
682 B
Text
34 lines
682 B
Text
|
|
running 103 tests
|
|
abc --- FAILED
|
|
....................................................................................... 88/103
|
|
............. 101/103
|
|
foo --- FAILED
|
|
foo2 --- FAILED
|
|
|
|
failures:
|
|
|
|
---- abc stdout ----
|
|
|
|
thread 'abc' ($TID) panicked at $DIR/terse.rs:12:5:
|
|
explicit panic
|
|
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace
|
|
|
|
---- foo stdout ----
|
|
|
|
thread 'foo' ($TID) panicked at $DIR/terse.rs:17:5:
|
|
explicit panic
|
|
|
|
---- foo2 stdout ----
|
|
|
|
thread 'foo2' ($TID) panicked at $DIR/terse.rs:22:5:
|
|
explicit panic
|
|
|
|
|
|
failures:
|
|
abc
|
|
foo
|
|
foo2
|
|
|
|
test result: FAILED. 100 passed; 3 failed; 0 ignored; 0 measured; 0 filtered out; finished in $TIME
|
|
|