Hi Suifan,
Thanx for the reply. I was looking thru the knowledgeBase to find
where these bugcodes are explained. It seems like they are taken offline.
Also I looked at the Win2k Kernel Debugging, and found that the
error
could occur if the thread is either attached to another process ( which is
by the way wrong, since it had to be attached with a process ) or a dpc is
under process. Now how could I get some more info about the DPC having only
the address ( I suppose ) of the DPC, ie the 4th arg on KeBugCheck*()
thx
prokash
-----Original Message-----
From: Suifun Law [mailto:suifun@us.ibm.com]
Sent: Monday, April 29, 2002 3:34 PM
To: Kernel Debugging Interest List
Subject: [windbg] Re: How to interpret bug code number 5 - Invalid Ke
Process Attach a ttempt
If a thread is executing a DPC, the 4th arg may be the address of the DPC.
Suifun
Prokash Sinha
To: “Kernel
Debugging Interest List”
Sent by: cc:
bounce-windbg-5602@li Subject: [windbg] How to
interpret bug code number 5 - Invalid Ke Process Attach a
sts.osr.com ttempt
04/29/2002 01:57 PM
Please respond to
“Kernel Debugging
Interest List”
Hi All,
As per the bug code 5, I find that the this could happen —
if the thd we are trying to attach is already
attached to a
different process, or
if the thd is running a DPC.
Then the 4th arg says - a flag indicating whether the thread
is
executing a DPC.
Here in 4th arg I get something like - ed427ff8. WHAT DOES IT
MEAN ?
Should it be
zero if the thread is not executing a DPC ???
thanx
proksh
—
You are currently subscribed to windbg as: suifun@us.ibm.com
To unsubscribe send a blank email to %%email.unsub%%
—
You are currently subscribed to windbg as: xxxxx@zonelabs.com
To unsubscribe send a blank email to %%email.unsub%%