Missing thread?

WINDBG
1

Hi,
Recently I have debugged a “frozen” 2-CPU SMP system. Problem was because 2
threads, each on its CPU were spinning around same spin lock. What I would
like to ask here, is why I don’t see both “RUNNING” threads in “!process 0
7”?
“!process 0 7” allways dumps only one RUNNING thread in my “frozen” case. I
need to use “!pcr 0” and “pcr 1” to get “Current thread” from both CPU’s and
then with “!thread xx” get the call stack for both (RUNNING) threads. If I
then back-search in “!process 0 7” dump for “Current thread” handles from
“!pcr”, I find only one, the other is hidden (or missing) in “!process 0 7”
dump.
Is this OK? I’m using WinDbg version 6.1.0017.2 and target PC is SMP
W2K-SP3.
Wbr Primoz

2

Is one of the threads an IDLE thread? If so, it will not show up in the
!process 0 7 list, because it does not belong to a “real” process.

Regards,

Tony

Tony Mason
Consulting Partner
OSR Open Systems Resources, Inc.
http://www.osr.com

-----Original Message-----
From: Primoz Beltram [mailto:xxxxx@hermes.si]
Sent: Tuesday, July 01, 2003 9:42 AM
To: Kernel Debugging Interest List
Subject: [windbg] Missing thread?

Hi,
Recently I have debugged a “frozen” 2-CPU SMP system. Problem was because 2
threads, each on its CPU were spinning around same spin lock. What I would
like to ask here, is why I don’t see both “RUNNING” threads in “!process 0
7”?
“!process 0 7” allways dumps only one RUNNING thread in my “frozen” case. I
need to use “!pcr 0” and “pcr 1” to get “Current thread” from both CPU’s and
then with “!thread xx” get the call stack for both (RUNNING) threads. If I
then back-search in “!process 0 7” dump for “Current thread” handles from
“!pcr”, I find only one, the other is hidden (or missing) in “!process 0 7”
dump.
Is this OK? I’m using WinDbg version 6.1.0017.2 and target PC is SMP
W2K-SP3.
Wbr Primoz

You are currently subscribed to windbg as: xxxxx@osr.com
To unsubscribe send a blank email to xxxxx@lists.osr.com

3

Yes, the *missing* running thread handle is equal for “CurrentThread” and
“IdleThread”. Thanks. Wbr Primoz

!pcr 1
…
CurrentThread: 82038588
NextThread: 820313a0
IdleThread: 82038588

-----Original Message-----
From: Tony Mason [mailto:xxxxx@osr.com]
Sent: Tuesday, July 01, 2003 4:09 PM
To: Kernel Debugging Interest List
Subject: [windbg] RE: Missing thread?

Is one of the threads an IDLE thread? If so, it will not show
up in the !process 0 7 list, because it does not belong to a
“real” process.

Regards,

Tony

Tony Mason
Consulting Partner
OSR Open Systems Resources, Inc.
http://www.osr.com

-----Original Message-----
From: Primoz Beltram [mailto:xxxxx@hermes.si]
Sent: Tuesday, July 01, 2003 9:42 AM
To: Kernel Debugging Interest List
Subject: [windbg] Missing thread?

Hi,
Recently I have debugged a “frozen” 2-CPU SMP system. Problem
was because 2 threads, each on its CPU were spinning around
same spin lock. What I would like to ask here, is why I don’t
see both “RUNNING” threads in “!process 0 7”?
“!process 0 7” allways dumps only one RUNNING thread in my
“frozen” case. I need to use “!pcr 0” and “pcr 1” to get
“Current thread” from both CPU’s and then with “!thread xx”
get the call stack for both (RUNNING) threads. If I then
back-search in “!process 0 7” dump for “Current thread”
handles from “!pcr”, I find only one, the other is hidden (or
missing) in “!process 0 7” dump. Is this OK? I’m using WinDbg
version 6.1.0017.2 and target PC is SMP W2K-SP3. Wbr Primoz

You are currently subscribed to windbg as: xxxxx@osr.com
To unsubscribe send a blank email to xxxxx@lists.osr.com

You are currently subscribed to windbg as:
xxxxx@hermes.si To unsubscribe send a blank email to
xxxxx@lists.osr.com