WinDbg symbol Table problem

1. Set the symbol table path First

Add a _nt_symbol_path value to srv*d:\symbols*http://msdl.microsoft.com/download/symbols in the system environment variable

This way Ida, WinDbg, vs will automatically load the symbol table into that directory.

For this path d:\symbols, you can customize any location, it is best not to use the offline symbol table, because you simply cannot find the corresponding system version, and

For WIN10 and other systems that are still in the update, the symbol table will change over time, and then re-download a multi-g symbol table, instead of trouble.

2. Symbols for all different versions of the operating system can be placed under the same directory d:\symbols.

Why?

I have tested that the symbol table of the same file will generate a different folder named after the hash value in the target directory, for example ntkrnlmp.pdb:

For these 2 folders, one is native win10, and one is Win7 64-bit system, so if there is XP, WIN8, or even different newer version of WIN10 this ntkrnlmp.pdb

Symbol table, there will be multiple folders corresponding to different versions, so there is no need to worry about conflicts.

3. Set the symbol table path or error

Solution:

(1) First network can pass, directly in the browser access http://msdl.microsoft.com/download/symbols see can open

(2) For debug targets, such as XP and Win7 64-bit systems, different versions of WinDbg should be used, for example XP can use 6. X version of the 32-bit WinDbg for kernel debugging

The Win7 64-bit is best used with a 64-bit 10.X version of WinDbg debugging. Otherwise, if you debug Win7 with a 32-bit 6.x version, the 64-bit will appear in the directory where the symbol table is stored to download the symbol table

But only 1KB size, obviously wrong, at that time this problem tangled me for a long time, and then replaced the 64-bit 10.X version of the WinDbg set the symbol table path automatically solve the problem

WinDbg symbol Table problem