Hi !
“ALL that debug dump” could be anything … processes, threads,
registers, memory contents … what do you want to look at? i mean, if
your driver is responsible for a crash, you may want to look at say,
what threads are running, what memory it touches, and then there will be
appropriate debugger commands to run. So, then you can fish out for the
documents that describe those commands…
The dump has a lot of information, and you may not want to look at
everything at the same time.
Download the windows debugger - WinDbg, and its help has lots of
information on how to analyze crash dumps. (I have not read the SoftIce
help, and so I cannot comment on that, but I am sure it should have good
info as well)
-g
-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of vartika Singh
Sent: Wednesday, August 04, 2004 12:14 PM
To: Windows System Software Devs Interest List
Subject: RE: [ntdev] Help ------------ Debug Info
I did ask a generic question.
But i did mention that i have got Visual SoftIce.
And i asked,‘how to interpret all that debug dump…?’.
Thus, I have got a debugger up and running.
Basically books/docs telling me how and what to infer
from that dump.
Cheers and Regards
V.S.
Do you Yahoo!?
Yahoo! Mail - Helps protect you from nasty viruses.
http://promotions.yahoo.com/new_mail
Questions? First check the Kernel Driver FAQ at
http://www.osronline.com/article.cfm?id=256
You are currently subscribed to ntdev as: xxxxx@cisco.com
To unsubscribe send a blank email to xxxxx@lists.osr.com