Determining owner of lock

  • Thread starter Thread starter Adam Benson
  • Start date Start date
A

Adam Benson

Hi,

An app deadlocked and I took a full process dump of it using cdb. I can see
no end of threads backed waiting for a lock on an object but no thread seems
to own the lock - they all seem to be stuck on the lock(me) statement.

Using Wnddbg or cdb is there any way to dig down and discover who has the
lock on that object ?

Thanks,

Adam.


==============================
(e-mail address removed)
 
| Hi,
|
| An app deadlocked and I took a full process dump of it using cdb. I can
see
| no end of threads backed waiting for a lock on an object but no thread
seems
| to own the lock - they all seem to be stuck on the lock(me) statement.
|
| Using Wnddbg or cdb is there any way to dig down and discover who has the
| lock on that object ?
|
| Thanks,
|
| Adam.
|
|
| ==============================
| (e-mail address removed)
|
|

Try using the sos.dll extention, and the !syncblbk command. Anyway you have
a couple of threads waiting on each other.

Willy.
 
Thanks, Willy,

I didn't realise that command existed in SOS.
I gave it a try but the app seemed to be jammed in MS code during an
object's serialisation.

All other threads were backed up waiting to get at the object being
serialise.

Regards,

Adam.
========
 
Back
Top