Analysing crash dump in windbg

Question

I am using a third party closed source API which throws an exception stating that \"all named pipes are busy\".

I would like to debug this further (rather than just step

Answer 1

You could start doing as follows to get an overview of the exception:

!analyze -v

Now you could load the exception context record:

.ecxr

And now... just take a look at the stack, registers, threads,...

kb     ;will show you the stack trace of the crash.
dv     ;local variables

Depending on the clues you get, you should follow a different direction. If you want a quick reference to WinDbg I'd recommend you this link.

I hope you find some of this commands and info useful.