Debugging exceptions in managed code using Windbg

Debugging exceptions in managed code using Windbghttp://blogs.msdn.com/kristoffer/archive/2007/01/03/debugging-exceptions-in-managed-code-using-windbg.aspxBy default Windbg will break for access violations (or null reference exceptions as they're called in managed code). To get Windbg to break for managed exceptions use the sxe command. 0:004> sxe clr 0:004> g A little while later our program generatesen-USCommunityServer 2.1 SP1 (Build: 61025.2)re: Debugging exceptions in managed code using Windbghttp://blogs.msdn.com/kristoffer/archive/2007/01/03/debugging-exceptions-in-managed-code-using-windbg.aspx#2395318Thu, 03 May 2007 18:09:08 GMT91d46819-8472-40ad-a661-2c78acb4018c:2395318Oisin Grehan<p>Using SOS for clr 1.1, there is no !printexception extension unfortunately -- what do we use instead? (newb to windbg)</p> <p>thanks!</p> <p>- Oisin</p> <p><a rel="nofollow" target="_new" href="http://www.codeplex.com/PowerShellCX">http://www.codeplex.com/PowerShellCX</a></p> <p><a rel="nofollow" target="_new" href="http://www.codeplex.com/PSSharePoint">http://www.codeplex.com/PSSharePoint</a></p> <p><a rel="nofollow" target="_new" href="http://www.codeplex.com/PSEventing">http://www.codeplex.com/PSEventing</a></p>re: Debugging exceptions in managed code using Windbghttp://blogs.msdn.com/kristoffer/archive/2007/01/03/debugging-exceptions-in-managed-code-using-windbg.aspx#2395447Thu, 03 May 2007 18:22:07 GMT91d46819-8472-40ad-a661-2c78acb4018c:2395447Kristoffer<p>Dump the stack objects with !DumpStackObjects and then do a !DumpObj on the first exception you see.</p>