How do I find the lockholder (reader) of my ReaderWriterLock in windbg
I've got a dump of a .Net process that has hung due to a deadlock (the gui thread is no longer responding, and my logs show that some threads have stopped responding). I have taken a snapshot and am now looking through it in windbg, and all threads bar one are waiting for the last one. Looking at that one thread's stacktrace with !clrstack -p I can see that it is trying to aquire a write on a ReaderWriterLock
How do I tell which other thread holds that lock so I can start figuring out how the deadlock happened?
 apparently there was a command !rwlocks in the .Net1.1 sos.dll to help with this, but it isn't there in the .Net2.0 version. The hunt continues
I'm not absolutely sure but you might be able to use !SyncBlk to look at the sync block objects, if you invoke it without any arguments I think you should see the sync blocks that are owned by a thread.
If you have a sync block deadlock, the extension
I posted a simular topic a while back here, http://stackoverflow.com/questions/698442/using-c-is-it-possible-to-test-if-a-lock-is-held-on-a-file/867537#867537
I referenced a number of articles and such, but wait chain traversial (WCT) can help you, it's somewhat touchy but this msdn mag bugslayer article show's how to use WCT in windbg in a managed context.