You did almost everything that needs to be done.
First, instead of download and setting the symbols use the ".symfix"
command like this: ".symfix c:\symbols" this will set the sympath to
Microsoft's public symbols server and will make WinDbg download any
symbols necessary for its usage when it needs to do so.
After you do that do ".sympath += [Path to your app's symbols]" to add
the symbols path to the symbols of your app.
Then, load the SOS extension (its an extension to WinDbg) that handles
Managed code by running the following command ".load clr10\sos.dll" (if
it doesn't work, go the WinDbg folder and into the clr10 and copy the
full path to the SOS.dll).
Now, instead of using the "k" commands that you used to display the
native call stack, use "!clrstack" to dump the managed stack and all
the places where you saw just numbers like "0x2f70552" and "0x3630065"
will be shown in the clr stack.
Hope this helpes you.
Eran.
----------------------------------
http://dotnetdebug.blogspot.com - Advanced .NET Debugging Blog
The blog for WinDbg, SOS, Production Managed Debugging, Post Mortem
Debugging and tips, tricks and tutorials about the secrets of WinDbg
and its friends.
Adam Benson wrote:
Mind to be more explicit, "gobbledegook" isn't of great help here.
Did you try Windbg to analyze the dump instead of VS.
Windbg produced the same results. ie :
WARNING : Stack unwind information not available. Following frames may be
wrong.
ntdll!ZwDelayExecution+0xc
mscorwks+0c83c74
mscorwks+0c83cec
0x2f70552
0x3630065
etc etc
The thing is I have installed the symbols and set _NT_SYMBOL_PATH.
I set it to c:\windows\symbols off which are subdirectories : 16bit, acm,
ax, etc
Is that the right set up ?
Thanks,
Adam.
