Windbg - Cannot see line number in managed call stack

nachiket kamat

Hi, I am using Windbg to analyze a crash that was created from managed code. I am loading SOS and mscorwks and using the !pe command. I can see the managed callstack, with module and function names but no source file and line number information. I can see this information for native crashes, but not for managed. I don't know if it is the PDBs or something else. when I did lm, it says I have private pdb symbols for my managed app. Any help is highly appreciated. Thanks

2 Replies

Know the answer? Post it — somebody with the same question will find it here.

nachiket kamat17y ago
Thanks Roei for responding to my query. I'm trying to debug a crash dump that was created from managed code. I'm using correct symbols and using SOS to get the managed callstack. I learnt about SOSEX.dll, it displays the source file and linenumbers but it only works on a full dump. I have minidumps, so it's no good to me. Can you get linenumbers for managed minidumps using SOS?
Roei Bar17y ago
did you try these steps: cause i am getting the lines perfectly... Attach WinDbg to the relevant process (F6 and select the process). make sure the symbols paths are OK by calling .sympath. If you don't have the symbols for .NET and the rest of windows just type ".symfix c:\symbols" this will put a path to Microsoft's public symbols server and will download all relevant symbols into c:\symbols. If you have symbols of your own in some folder you can use .sympath with the += flag (like this .sympath += c:\mypath) to add the additional path. type ".load clr10\sos.dll" to load the SOS extension (it might already be loaded, but it won't do any harm calling it again). Run the command "!SyncBlk".