This is a very crude documentation only.
If you got "Module load completed but symbols could not be loaded for....." do the following to investigate:
This should pin point why debug symbols are not being loaded.
To use the Microsoft Symbol Server
1. Make sure you have installed the latest version of Debugging Tools for Windows.
2. Start a debugging session.
3. Decide where to store the downloaded symbols (the "downstream store"). This can be a local drive or a UNC path.
4. Set the debugger symbol path as follows, substituting your downstream store path for DownstreamStore.
If you got "Couldn't load mismatched pdb for appname.exe", you can force Windbg to load the pdb file via:
To check if the symbols match:
If you got "Module load completed but symbols could not be loaded for....." do the following to investigate:
kd> !sym noisy kd> .reload
This should pin point why debug symbols are not being loaded.
To use the Microsoft Symbol Server
1. Make sure you have installed the latest version of Debugging Tools for Windows.
2. Start a debugging session.
3. Decide where to store the downloaded symbols (the "downstream store"). This can be a local drive or a UNC path.
4. Set the debugger symbol path as follows, substituting your downstream store path for DownstreamStore.
SRV*d:\msdndebug*http://msdl.microsoft.com/download/symbolsThis will download debug symbols to d:\msdndebug automatically.
If you got "Couldn't load mismatched pdb for appname.exe", you can force Windbg to load the pdb file via:
kd> .symopt 0x40 kd> .reload
To check if the symbols match:
~ts#>!itoldyouso bff c:\path\bin\bff.pdb
Comments