!locks

WINDBG
1

I am debugging a user mode application and when I use !locks, I get no
output. !locks -v does list all critical sections but all of them are of
this form

CritSec +9c020f8 at xxxxxxxx
LockCount NOT LOCKED
RecursionCount 0
OwningThread 0
EntryCount 0
ContentionCount 0

Is this right?

Thanks!

-Ajay Agrawal

You are currently subscribed to windbg as: $subst(‘Recip.EmailAddr’)
To unsubscribe send a blank email to leave-windbg-$subst(‘Recip.MemberIDChar’)@lists.osr.com

2

Sounds like it is working the way it is described in the docs. The user
mode !locks (called the one implemented in ntsdexts.dll) will give the
list critical section currently entered by the process. !locks -v will
list all critical sections in the process.

It makes sense that if you have no critical sections held that !locks
will just tell you how many critical sections scanned and that !locks -v
would just show you a much of unlocked critical sections.

If you are sure that your process is inside a critical section and there
is a bug in !locks then let me know. Otherwise read the docs to improve
your understanding of what this command does in UM.

-----Original Message-----
From: Ajay K Agrawal [mailto:xxxxx@themoment.com]
Sent: Wednesday, July 11, 2001 7:26 AM
To: Kernel Debugging Interest List
Subject: [windbg] !locks

I am debugging a user mode application and when I use !locks, I get no
output. !locks -v does list all critical sections but all of them are of
this form

CritSec +9c020f8 at xxxxxxxx
LockCount NOT LOCKED
RecursionCount 0
OwningThread 0
EntryCount 0
ContentionCount 0

Is this right?

Thanks!

-Ajay Agrawal

You are currently subscribed to windbg as: xxxxx@microsoft.com
To unsubscribe send a blank email to leave-windbg-$subst(‘Recip.MemberIDChar’)@lists.osr.com

You are currently subscribed to windbg as: $subst(‘Recip.EmailAddr’)
To unsubscribe send a blank email to leave-windbg-$subst(‘Recip.MemberIDChar’)@lists.osr.com

3

Thanks - I’ll reread the docs!

-Ajay

-----Original Message-----
From: Nathan Nesbit [mailto:xxxxx@windows.microsoft.com]
Sent: Wednesday, July 11, 2001 10:32 AM
To: Kernel Debugging Interest List
Subject: [windbg] RE: !locks

Sounds like it is working the way it is described in the docs. The user
mode !locks (called the one implemented in ntsdexts.dll) will give the
list critical section currently entered by the process. !locks -v will
list all critical sections in the process.

It makes sense that if you have no critical sections held that !locks
will just tell you how many critical sections scanned and that !locks -v
would just show you a much of unlocked critical sections.

If you are sure that your process is inside a critical section and there
is a bug in !locks then let me know. Otherwise read the docs to improve
your understanding of what this command does in UM.

-----Original Message-----
From: Ajay K Agrawal [mailto:xxxxx@themoment.com]
Sent: Wednesday, July 11, 2001 7:26 AM
To: Kernel Debugging Interest List
Subject: [windbg] !locks

I am debugging a user mode application and when I use !locks, I get no
output. !locks -v does list all critical sections but all of them are of
this form

CritSec +9c020f8 at xxxxxxxx
LockCount NOT LOCKED
RecursionCount 0
OwningThread 0
EntryCount 0
ContentionCount 0

Is this right?

Thanks!

-Ajay Agrawal

You are currently subscribed to windbg as: xxxxx@microsoft.com
To unsubscribe send a blank email to leave-windbg-$subst(‘Recip.MemberIDChar’)@lists.osr.com

You are currently subscribed to windbg as: xxxxx@themoment.com
To unsubscribe send a blank email to leave-windbg-$subst(‘Recip.MemberIDChar’)@lists.osr.com

You are currently subscribed to windbg as: $subst(‘Recip.EmailAddr’)
To unsubscribe send a blank email to leave-windbg-$subst(‘Recip.MemberIDChar’)@lists.osr.com