Software Diagnostics Library

I was recently asked to provide explanation on how to analyze the output of !locks command in kernel and complete memory dumps and I compiled these patterns:

• _ERESOURCE Deadlock
• Mixed Object Deadlock
• Self Deadlock
• High Contention
• Accidental Lock
• _ERESOURCE Wait Chain
• Swarm of Shared Locks
• Semantic Split
• Livelock

and case studies:

http://www.dumpanalysis.org/blog/index.php/2008/07/17/multiple-patterns-in-a-dump-case-study/

http://www.dumpanalysis.org/blog/index.php/2008/10/29/10-common-mistakes-in-memory-analysis-part-3/

http://www.dumpanalysis.org/blog/index.php/2008/12/12/wait-chain-and-spiking-thread-pattern-cooperation/

http://www.dumpanalysis.org/blog/index.php/2009/02/16/insufficient-memory-handle-leak-process-factory-high-contention-and-busy-system-pattern-cooperation/

http://www.dumpanalysis.org/blog/index.php/2009/03/03/busy-system-blocked-threads-wait-chains-and-deadlock-pattern-cooperation/

http://www.dumpanalysis.org/blog/index.php/2009/12/17/wait-chain-blocked-thread-waiting-thread-time-irp-distribution-anomaly-and-stack-trace-collection-pattern-cooperation/

http://www.dumpanalysis.org/blog/index.php/2010/02/27/inconsistent-dump-stack-trace-collection-lpc-thread-process-executive-resource-wait-chains-missing-threads-and-waiting-thread-time-pattern-cooperation/

http://www.dumpanalysis.org/blog/index.php/2010/06/03/succession-of-patterns-part-2/

- Dmitry Vostokov @ DumpAnalysis.org + TraceAnalysis.org -

This entry was posted on Monday, November 7th, 2011 at 8:43 am and is filed under Crash Dump Analysis, Crash Dump Patterns, Debugging, Object Patterns. You can follow any responses to this entry through the RSS 2.0 feed. You can leave a response, or trackback from your own site.