[SERVER-27875] Dump critical sections on Windows in hang_analyzer.py Created: 31/Jan/17 Updated: 07/Sep/17 Resolved: 21/Feb/17 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Testing Infrastructure |
| Affects Version/s: | None |
| Fix Version/s: | 3.4.4, 3.5.4 |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Jonathan Abrahams | Assignee: | Eddie Louie |
| Resolution: | Done | Votes: | 0 |
| Labels: | bkp | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||
| Backwards Compatibility: | Fully Compatible | ||||
| Backport Requested: |
v3.4
|
||||
| Sprint: | TIG 2017-03-06 | ||||
| Participants: | |||||
| Description |
|
This can be done with !cs -l in CDB. It will at least capture Critical Sections but not ReaderWriterLockSlim. https://msdn.microsoft.com/en-us/library/windows/hardware/ff562294(v=vs.85).aspx |
| Comments |
| Comment by Githook User [ 13/Apr/17 ] | |||||||||||||||||||||||||||||||||||
|
Author: {u'username': u'elouie99', u'name': u'Eddie Louie', u'email': u'eddie.louie@mongodb.com'}Message: (cherry picked from commit baedb6631eeed584be827d3b430ecc0bd0a59654) | |||||||||||||||||||||||||||||||||||
| Comment by Githook User [ 21/Feb/17 ] | |||||||||||||||||||||||||||||||||||
|
Author: {u'username': u'elouie99', u'name': u'Eddie Louie', u'email': u'eddie.louie@mongodb.com'}Message: | |||||||||||||||||||||||||||||||||||
| Comment by Eddie Louie [ 18/Feb/17 ] | |||||||||||||||||||||||||||||||||||
|
Thanks max.hirschhorn for putting up the SERVER-26270 deadlock repro. I added the '!cs -l' option to CDB and it nicely prints out this critical section information for all locked critical sections. Note: The -l option is to print only locked critical sections.
|