-
-
Notifications
You must be signed in to change notification settings - Fork 17.2k
regression: thread names missing from stack overflow error messages #144481
Copy link
Copy link
Closed
Labels
A-thread-localsArea: Thread local storage (TLS)Area: Thread local storage (TLS)C-bugCategory: This is a bug.Category: This is a bug.T-libsRelevant to the library team, which will review and decide on the PR/issue.Relevant to the library team, which will review and decide on the PR/issue.regression-from-stable-to-betaPerformance or correctness regression from stable to beta.Performance or correctness regression from stable to beta.
Description
Activity
Metadata
Metadata
Assignees
Labels
A-thread-localsArea: Thread local storage (TLS)Area: Thread local storage (TLS)C-bugCategory: This is a bug.Category: This is a bug.T-libsRelevant to the library team, which will review and decide on the PR/issue.Relevant to the library team, which will review and decide on the PR/issue.regression-from-stable-to-betaPerformance or correctness regression from stable to beta.Performance or correctness regression from stable to beta.
Thread names have gone missing in stack overflow messages in Rust v1.89 (currently in beta). Reproduces on both Darwin and Linux.
I haven't bisected, but the culprit is almost certainly #140628. Nothing else has touched the stack overflow code path since Rust v1.88. cc @joboet @workingjubilee @RalfJung @Mark-Simulacrum as the reviewers of #140628.
Code
I tried this code:
I expected to see the thread name (
main) included in the error message:Instead, the thread is listed as
<unknown>:Version it worked on
Works on the latest stable Rust (v1.88.0).
Version with regression
Broken in v1.89.0-beta.7. Tested on both Darwin and Linux.
@rustbot modify labels: +regression-from-stable-to-beta -regression-untriaged