[SERVER-36629] Hang analyzer should print what threads are holding or blocked on spinlocks Created: 13/Aug/18  Updated: 27/Oct/23  Resolved: 16/Aug/18

Status: Closed
Project: Core Server
Component/s: Testing Infrastructure
Affects Version/s: None
Fix Version/s: None

Type: Improvement Priority: Major - P3
Reporter: Spencer Brody (Inactive) Assignee: DO NOT USE - Backlog - Test Infrastructure Group (TIG)
Resolution: Gone away Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
depends on SERVER-36628 SpinLock should remember what thread ... Closed
Participants:

 Comments   
Comment by Max Hirschhorn [ 16/Aug/18 ]

Closing this as "Gone away" because we elected to not do SERVER-36628 and std::mutex is already handled by logging the owner should a hang involving SpinLock come up on a Linux --dbg=on build.

Comment by Mira Carey [ 16/Aug/18 ]

I think this may "just work" in debug builds.

SERVER-36676 swaps out the backing logic in SpinLock for a mutex in debug builds, which should already have support in the hang analyzer.

Comment by Max Hirschhorn [ 13/Aug/18 ]

Putting this on the backlog until SERVER-36628 is implemented.

Generated at Thu Feb 08 04:43:40 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.