Crash dump - WinDbg - force PDB files to match doesn't work?

debugging windbg symbols crash-dumps
JosephA picture JosephA · Feb 19, 2014 · Viewed 15.8k times · Source

I have a crash dump for a customer's application built with a very old version of our dll (release build, don't have original symbols) that I've been analyzing in WinDbg.

In order to get more information, I rebuilt the dll in release mode, with symbols this time, using the same compiler version and I believe the same settings as when the dll was originally built. I added the symbol file to my symbol path, but the WinDbg extension !itoldyouso tells me the module in the dump doesn't match the PDB file. Enabling SYMOPT_LOAD_ANYTHING doesn't help either.

!itoldyouso tells me they don't match because the module has no pdb sig (value 0), versus the recreated symbol file I made (with a valid pdb sig). How do I get them to match?

Answer

Marc Sherman picture Marc Sherman · Feb 19, 2014

Have you tried .reload /i foo.dll ?

For verbose output try:

!sym noisy;.reload /i foo.dll;x foo!*test*

Related questions

ERROR: Symbol file could not be found. windbg.exe

I downloaded the symbols from http://www.microsoft.com/whdc/devtools/debugging/symbolpkg.mspx the package (Windows 7 RTM x86 retail symbols, all languages) but it still gives me the same error! Done .sympath but still not working .sympath C:\inetpub\…

Read More
WinDbg symbol resolution

When using WinDbg, where should the private symbol files (pdb?) be placed? My situation is: I have a DLL which I want to debug. I have the source code and symbol files for this DLL. This DLL is called by …

Read More
How to set up symbols in WinDbg?

I am using Debugging Tools for Windows and I get the following error message when starting WinDbg / cdb or ntsd: Symbol search path is: *** Invalid *** **************************************************************************** * Symbol loading may be unreliable without a symbol search path. * * Use .symfix to have the …

Read More