WinDbg Instruction

[Mike Martinez]

I am new to using WinDbg and I would like to learn more about how to use the
program. I have read many dump files and can rarely decipher the issues
unless the problem slaps you in the face. Please be kind.
--
Mike Martinez

[Greg Nagel]

Hi Mike

Check out Tess's blog, it's a brilliant source of information.

http://blogs.msdn.com/tess/

Cheers

Greg

"Mike Martinez" <MikeMa...@discussions.microsoft.com> wrote in message
news:4731E6FD-0550-4E1D...@microsoft.com...

[Scott Noone]

It's definitely tough to get started. The problem is that in order to
successfully root cause Windows system crashes you first and foremost need
to understand both Windows and the architectures on which Windows runs. From
there, you need to learn to use the tools available to extract the
information necessary to find the cause. All of these are difficult and can
require significant ramp up time.

So, my recommendations for those getting started always include:

1) Read the Windows internals book several times (ISBN: 0735619174). This
will start to get you comfortable with the Windows architecture

2) The debugging package installs a tutorial that has good getting started
information (kernel_debugging_tutorial.doc). This will start to get you
comfortable with how to use the debugger.

3) In The Basics section on OSR Online we had a series a while ago titled
"Bugchecks Explained" http://www.osronline.com/section.cfm?section=26. This
covers some common bugcheck codes and walks through how we solved examples
of them in the debugger, it might be helpful as a reference to those getting
started.

4) Practice. Debugging is self reinforcing, so the more you do it the better
you get. I always recommend telling your friends/family/significant other(s)
to enable crash dumps on their systems and send them to you whenever they
crash. It's a good way to practice and if you figure it out you'll be their
hero

The good news is that if you get into it debugging crash dumps can be quite
fun. It's sort of the closest thing we devs get to playing CSI, the dump is
the crime scene and we need to reconstruct the scenario that led us here :)
And remember that no one came out of the womb knowing how to analyze dumps,
we all started somewhere!

Good luck!

-scott

--
Scott Noone
Consulting Associate
OSR Open Systems Resources, Inc.
http://www.osronline.com

Looking forward to seeing you at the next OSR Kernel Debugging Class April
6, 2009 in Portland, OR!

"Mike Martinez" <MikeMa...@discussions.microsoft.com> wrote in message
news:4731E6FD-0550-4E1D...@microsoft.com...

[Mike Martinez]

Thanks Greg. Does anyone else have anymore info? Please.
--
Mike Martinez

[Avi Cohen Stuart]

Mike,

There is a book called "Advanced Windows Debugging". If you are going to use
windbg more often in the near future as part of your work,. this book should
be standard on your desk
Here is the website: http://advancedwindowsdebugging.com/

Avi.

"Mike Martinez" <MikeMa...@discussions.microsoft.com> wrote in message
news:4731E6FD-0550-4E1D...@microsoft.com...

[Mike Martinez]

Thanks Scott!!
--
Mike Martinez

[Dan Thompson [MSFT]]

The book I wish I would have had when I started learning: "Advanced Windows
Debugging" by Mario Hewardt and Daniel Pravat.

You should read the Windows Internals book first, but once you've done that,
don't let the "Advanced" in the title intimidate you. It's very practical.

"Scott Noone" <sno...@osr.com> wrote in message
news:OvsgwYCm...@TK2MSFTNGP02.phx.gbl...

[johndoe]

in addition,

I would suggest you start from instruction set, and try to read the
disambly.

then try to use d, x, uf, t etc. get your hands dirty. before this, you need
to
setup the symbols path, as well as set up the debug enviorenment.

"Mike Martinez" <MikeMa...@discussions.microsoft.com> wrote in message
news:4731E6FD-0550-4E1D...@microsoft.com...