Use windbg to view dump files

Download windbg

 

The latest program automatically jumps out of the client.

Check the code.

Start to study how to view dump files.

 

Select compilation settings

After rebuildall, create the same path as the path of the client program locally. For example, the path of the file to be debugged on the client is D:/test/test1.exe.

Create the same directory locally and copy the generated PDB file and test1.exe to the corresponding local directory.

Do not change the code until the debugging ends. (For windbg, EXE, PDB, and source code time, work well)

 

Upload test1.exe to the client

 

Run the program to be captured on a remote machine (test1.exe)

Start the command line and enter the windbg installation folder (* 1)

Run

Adplus-crash-PN test1.exe-o C:/dumps

If there is a Waring prompt, follow OK

 

 

In this example, when test1.exe fails, the DMP file will be crawled under C:/dumps.

Copy to any part of the local machine, use windbg to open the wait> prompt to press K to see the stack call before jumping out (windbg needs to set the symbol server first:

Open windbg, press Ctrl + S, enter SRV * C:/websymbols * http://msdl.microsoft.com/download/symbols)

 

Note: The local directory EXE and the PDB file must correspond to the EXE file that generates the dump file.

 

Note 1: the remote host is installed with the adplus to capture the crash dump.