about summary refs log tree commit diff
path: root/tests/debuginfo/function-arg-initialization.rs
diff options
context:
space:
mode:
authorbors <bors@rust-lang.org>2025-08-07 02:32:55 +0000
committerbors <bors@rust-lang.org>2025-08-07 02:32:55 +0000
commit61cb1e97fcf954c37d0a457a8084ed9ad8b3cb82 (patch)
tree107887d30f4041adae19af258f83ca2dc0fb5d93 /tests/debuginfo/function-arg-initialization.rs
parent6bcdcc73bd11568fd85f5a38b58e1eda054ad1cd (diff)
parent289fe36d373c5a13fa7f1b93f39ff88425ab2351 (diff)
downloadrust-61cb1e97fcf954c37d0a457a8084ed9ad8b3cb82.tar.gz
rust-61cb1e97fcf954c37d0a457a8084ed9ad8b3cb82.zip
Auto merge of #115746 - tgross35:unnamed-threads-panic-message, r=cuviper
Print thread ID in panic message

`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>' (12345) 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.

try-job: aarch64-apple
try-job: aarch64-gnu
try-job: dist-apple-various
try-job: dist-various-*
try-job: dist-x86_64-freebsd
try-job: dist-x86_64-illumos
try-job: dist-x86_64-netbsd
try-job: dist-x86_64-solaris
try-job: test-various
try-job: x86_64-gnu
try-job: x86_64-mingw-1
try-job: x86_64-msvc-1
Diffstat (limited to 'tests/debuginfo/function-arg-initialization.rs')
0 files changed, 0 insertions, 0 deletions