WinDbg analysis dump file

Debugging ability can be said to be the most important , Especially for C/C++ For programmers , Even more so ！

Use artifact WinDbg debugging Dump Documents need three things ：

1. Beyond all doubt , Must be Dump It's a document

2. Source code , It must be consistent with the code when compiling the executable

3.PDB file , Symbol file generated at compile time , It must be generated at the same time as the executable ！（ Even if the source code is consistent , Regenerated PDB Documents are not good either .）

1、 use WinDbg open dump file

2、 Set symbol path （ Corresponding when generating binary files PDB Where are the documents Catalog , The version should be consistent ！ Of multiple binaries pdb It's best to be born in the same directory ）：

3、 Set the source code path （ Project solution Where are the documents Catalog , Multiple items can be added to one solution Inside ）：