CODEWITHSUNDEEP
c#.netwindbg
George2
George2

Reputation: 45771

WinDbg symbol load issue

I am using WinDbg to load a crash dump from managed code (C#, a console application built for Any CPU). I am debugging on a x64 platform. I have put the related PDB file into the symbol path.

But when I use the lm command to see load models, the symbol of the console EXE file application can not be loaded. I have tried to execute .reload /f, but I still cannot load the symbol for my application.

BTW: I have the full source code for my application. My application is built for .NET 3.0, but the machine I am working on to debug is installed with lastest .NET 3.5 + SP1. Could the mismatch be the issue?

How do I analyze this problem further?

Upvotes: 0

Views: 1325

Answers (1)

Kris Kumler
Kris Kumler

Reputation: 6307

To start with, I would try using !sym noisy and then reloading the module. You should see information for the module that it is trying to load. If you have a local cache, a common status you may see is E_PDB_CORRUPT. First delete the symbol file from the local cache and then use .reload /f.

If it can't find the symbol, ensure you have the proper symbol packages available or Use the Microsoft Symbol Server to obtain debug symbol files.

Upvotes: 1

Related Questions