Crash Dump Analysis Patterns (Part 9f)

This is a variation of a deadlock pattern where a thread that owns a resource (either in shared or exclusive mode) attempts to acquire it exclusively again. This results in a self-deadlock:

Resource @ 0x85d9c018    Shared 1 owning threads
    Contention Count = 2
    NumberOfExclusiveWaiters = 2
     Threads: 85db0030-02<*>
     Threads Waiting On Exclusive Access:
              85f07d78       85db0030

- Dmitry Vostokov @ + -

3 Responses to “Crash Dump Analysis Patterns (Part 9f)”

  1. Crash Dump Analysis » Blog Archive » Icons for Memory Dump Analysis Patterns (Part 83) Says:

    […] Crash Dump Analysis Exploring Memory Dumps, Software Tracing, Debugging and Malware Analysis Techniques « Crash Dump Analysis Patterns (Part 9f) […]

  2. Lenka Says:

    I think this can happen only if the resource has been first acquired as shared and then exclusively.
    According to WDK resources support recursive locking. The only scenario which is not supported (and which causes deadlocks) is acquiring a resource as shared and then exclusively.

  3. Dmitry Vostokov Says:

    Thanks for pointing this out!

Leave a Reply

You must be logged in to post a comment.