Crash analysis in windbg

Question

I use a third-party, closed-source API that throws an exception that says "all named pipes are busy."

I would like to debug this further (and not just step over) so that I can really find out what is happening under the covers.

I took a dump of this process using WinDbg. What commands should be used to analyze this dump?

thanks

Answer 1

You can start by doing the following to get an overview of the exception:

!analyze -v

Now you can load the exception context entry:

.ecxr

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

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

, , . WinDbg, .

, .

Answer 2

postmortem Windbg, , , . :

.logopen <filename>    (See also .logappend)
.lastevent             See why the process halted and on what thread
u                      List disassembly near $eip on offending thread
~                      Status of all threads
Kb                     List callstack, including parameters
.logclose

, , . , , # , , .

Answer 3

, CreateFile , . CreateFile , - ERROR_PIPE_BUSY. - WaitNamedPipe , , .

, .

Answer 4

WinDbg , : http://www.networkworld.com/article/3100370/windows/how-to-solve-windows-10-crashes-in-less-than-a-minute.html

Windows 10, Windows.

Answer 5

, DLL ( Reflector)

WinDbg , Process-Monitor (SysInternals, freeware) . - , , , .

Process-Monitor , . , - DLL, pdb's.

k ( , , ). - DLL, , , , . , API Win32 - , dll, , - "". dll, (dv), .

, .