> Deadlock detection was one of my favorite features of OSR’s driver
debugging
toolking (OSR DDK) for NT V4. Verifier now automagically watches your
lock
acquisitions and releases, and builds an actual locking hierachy based on
your driver’s behaviour. If during execution, your driver violates this
hierarchy Verifier catches this.
Does this thing work for ERESOURCE locks?
Max
You are currently subscribed to ntdev as: $subst(‘Recip.EmailAddr’)
To unsubscribe send a blank email to leave-ntdev-$subst(‘Recip.MemberIDChar’)@lists.osr.com