Ureader.com  
Microsoft software help and Community
   home   |   control panel login   |   archive   |  
 
tools
vsnet.act
vsnet.debugging
vsnet.documentation
vsnet.enterprise.tools
vsnet.general
vsnet.ide
vsnet.jlca
vsnet.servicepacks
vsnet.setup
vsnet.vsip
vsnet.vss
vsnet.vstools.office
vstudio.development
vstudio.extensibility
vstudio.general
vstudio.helpauthoring
vstudio.setup
vstudio.sourcesafe
  
 
date: Thu, 3 Jul 2008 11:34:52 +1000,    group: microsoft.public.vsnet.debugging        back       


Getting managed call stack from a crash dump   
Hi,

Is there any way I could get my managed code call stack when my 
managed+unmanaged application crashes? (I am using managed code under MMC 
3.0). You know when it pops up with a suggestion to report the problem to 
MS, can I somehow see the call stack ?

//Misha
date: Thu, 3 Jul 2008 11:34:52 +1000   author:   Mikhail

Re: Getting managed call stack from a crash dump   
"Mikhail"  wrote in message 
news:elEL$zK3IHA.3500@TK2MSFTNGP05.phx.gbl...
> Hi,
>
> Is there any way I could get my managed code call stack when my 
> managed+unmanaged application crashes? (I am using managed code under MMC 
> 3.0). You know when it pops up with a suggestion to report the problem to 
> MS, can I somehow see the call stack ?
>
> //Misha

Hi Misha,
you can set up windows reporting to generate a dump file on every crash. 
Open the dump file with WinDbg and load the sos extention to get managed 
commands loaded in WinDbg. Use !clrstack or !dumpstack commands to see your 
currect thread stack.
You can also see all threads using the !threads command and change the 
active thread with ~<threadnumber>s.
There is a tool from Ingo Rammer called SOSAsisst which automates most of 
these commands for you.

Good luck,
Martin Kulov
www.kulov.net
date: Wed, 30 Jul 2008 11:19:33 +0300   author:   Martin Kulov [MVP] am

Google
 
Web ureader.com


    COPYRIGHT 2007, YARDI TECHNOLOGY LIMITED, ALL RIGHT RESERVE  |   contact us