Prev: Keyboard HID minidriver
Next: Printer Driver using WINDDK OEMUI.DLL
From: Zaheer on 7 Dec 2009 02:18

Hi,

I am trying to debug the crash dump using Windbg.
A few doubts regarding using Windbg.

1) Can I debug the crash using single PC
or one extra PC is required for debugging.

Any tutorials on how to use windbg are welcome.

Regards in anticipation of your replies,
Zaheer.


Submitted via EggHeadCafe - Software Developer Portal of Choice
Book Review: Practical .NET2 and C#2 - by Patrick Smacchia
http://www.eggheadcafe.com/tutorials/aspnet/dec2a779-a703-4e95-80cf-e9356835c4d7/book-review-practical-n.aspx
From: Burkhardt Braun on 7 Dec 2009 04:53
Hello,
On Dec 7, 7:18 am, Zaheer Khan wrote:
> Hi,
>
> I am trying to debug the crash dump using Windbg.
> A few doubts regarding using Windbg.
>
> 1) Can I debug the crash using single  PC
not really debugging, but windbg is able to "estimate" the crash
reason
( code line ) if you have the dump file, the symbols and the sources
on your PC.

> or one extra PC is required for debugging.
Yes.

>
> Any tutorials on how to use windbg are welcome.
You might take a look at http://www.codeproject.com/KB/debug/windbg_part1.aspx
and the following parts.
Burkhardt Braun


>
> Regards in anticipation of your replies,
> Zaheer.
>
> Submitted via EggHeadCafe - Software Developer Portal of Choice
> Book Review: Practical .NET2 and C#2 - by Patrick Smacchiahttp://www.eggheadcafe.com/tutorials/aspnet/dec2a779-a703-4e95-80cf-e...

From: Pavel A. on 7 Dec 2009 12:21
"Zaheer Khan" wrote in message news:200912721819mdzkhan(a)yahoo.com...
>
> Hi,
>
> I am trying to debug the crash dump using Windbg.
> A few doubts regarding using Windbg.
>
> 1) Can I debug the crash using single PC
> or one extra PC is required for debugging.

For debuggin a dump, the 2nd machine is not needed.
Just run windbg, open the dump and download the OS symbols as explainded in
windbg help file.

> Any tutorials on how to use windbg are welcome.

After you install the debugging tools, run windbg and read the "getting
started" section in the windbg help file,
then Debugging techniques and Advanced Debugging techniques on use of the
!analyze command.

Also, read kernel_debugging_tutorial.doc in the directory where windbg is
installed.

God luck,
--pa


From: Maxim S. Shatskih on 8 Dec 2009 08:31
> 1) Can I debug the crash using single PC

Yes, you can.

"windbg -z DumpFileName", or start WinDbg and drag-and-drop the dump file to it from the shell.

Then set up the symbols using !symfix, then !analyze -v and so on.

--
Maxim S. Shatskih
Windows DDK MVP
maxim(a)storagecraft.com
http://www.storagecraft.com

 | 
Pages: 1
Prev: Keyboard HID minidriver
Next: Printer Driver using WINDDK OEMUI.DLL