CODEWITHSUNDEEP
c++debuggingvisual-studio-2013
Luko28
Luko28

Reputation: 11

VS 2013 missing symbols (msvcr120.i386.pdb)

I have a very frustrating problem, I'm debugging my code, and for complete Call Stack I need to get symbols for msvcr120.dll (msvcr120.i386.pdb).

The thing is, that I can't get it.

SYMSRV: http://msdl.microsoft.com/download/symbols/msvcr120.i386.pdb/16F5E2EF340A453ABC8B8F67DC6FD8082/msvcr120.i386.pdb not found

http://msdl.microsoft.com/download/symbols: Symbols not found on symbol server.

msvcr120.i386.coresys.pdb

msvcr120_clr0400.i386.pdb

So, is there a way to get "msvcr120.i386.pdb" ?

Upvotes: 1

Views: 4914

Answers (1)

Craig Woodward
Craig Woodward

Reputation: 21

In order to get the proper PDB for the file, you need to know which module is actually loaded. If you create a crashdump (.DMP) of the program while running (which you can do with taskmanager), it should show you the exact file loaded, including it's full path. You can also use a tool like dependency walker, which may do a better job at finding the full path.

Once you have the path, you can then specifically try to force-load symbols for that module by right-clicking, loading, and pointing to the exact file in question. That should get the proper hash and load the correct PDB from the MS symbol store into your local cache.

What's likely happening is that the program you're running either has a manifest calling out a specific SxS version of the DLL, OR your program has crashed enough that Windows has placed it in "compatibility mode". Either way, that means the program and VS are finding different versions of the DLL, thus the problem you're having. You can also see this when your program crashes on a different machine than the one you're debugging on, especially if they're not both exactly in the same place for windows updates.

If you do dev work regularly, you should disable Windows automatically putting things into compatibility mode. It will save you lots of headaches down the road.

Upvotes: 2

Related Questions