Windbg symbol load issue

views:

234

answers:

Windbg symbol load issue

Hello everyone,

I am using Windbg to load a crash dump from managed code (C#, a console application built for Any CPU). I am debugging on x64 platform. I have put the related pdb file into symbol path. But when I use lm command to see load models, the symbol of the console exe application can not be loaded. I have tried to execute .reload /f, but still cannot load the symbol for my application.

BTW: I have 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 the issue?

Any ideas to analyze further?

thanks in advance, George

+1 A:

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.

Kris Kumler 2009-10-11 02:50:55

If I need to display line number information of .cs file (when executing command like clrstack), do I need to set up source file path or not? My confusion is I am confused whether Windbg is capable to extract line number information from managed code (EXE/DLL) or related PDB file?

George2 2009-10-11 16:23:39

Thanks Kris, your reply gives me a lot of help. I have followed your advice but has a new issue, appreciated if you could take a look. My new issue is posted here,http://stackoverflow.com/questions/1552927/symbol-issue-when-debugging-c-code

George2 2009-10-12 05:53:02

ansaurus

tags:

views:

answers:

Windbg symbol load issue

related questions