`<shared_mutex>`: debug visualizer
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 11.1k
- Forks
- 1.7k
- Avg merge
- 4d 15h
- Merged PRs (30d)
- 22
Description
Today I helped my colleague to pinpoint deadlock cause in VS2015 project
It was 30 seconds debug session.
The first 10 seconds were as following:
But I think this feature seems to be lost for VS2019 .
What is more concerning, looks like it cannot be implemented for <shared_mutex>, since it is SRWLOCK based.
And I expect that vNext <mutex> will be the same, as I think it should be either SRWLOCK based or atomic wait based.
Is this correct that the goal of performance dominates here, so there will not be extra debug facilities, even in debug build? Any suggestions on deadlock debugging?
vNext note: Resolving this issue will require breaking binary compatibility. We won't be able to accept pull requests for this issue until the vNext branch is available. See #169 for more information.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reviewing the reported VS2015 and VS2019 behavior for and <shared_mutex>, then read the vNext compatibility note and issue #169. The issue does not name repository files or tests; completion would require an agreed debug-visualizer design that addresses SRWLOCK-based synchronization and binary compatibility.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- devtools, operating-systems
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100