Welcome to MSDN Blogs Sign in | Join | Help

January 2007 - Posts

Tuesday, January 09, 2007 9:08

Debugging memory usage in managed code using Windbg

Windbg, is there anything it can't do? CLR Profiler is great for getting an overview of memory allocations and usage for managed applications but it doesn't work for very large applications and can't be attached after the application has been running
Posted by Kristoffer | 1 Comments
Filed under:
Friday, January 05, 2007 8:35

Debugging lock issues in managed code using Windbg

Windbg can be helpful for locking lock issues in managed code that seem to only happen on client machines when the moon is full and the stars are aligned just right. Windbg is a minimal installation and with managed code doesn't require debug symbols
Posted by Kristoffer | 0 Comments
Filed under:
Wednesday, January 03, 2007 8:04

Debugging exceptions in managed code using Windbg

By 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 generates
Posted by Kristoffer | 2 Comments
Filed under:
Tuesday, January 02, 2007 8:49

Setting a breakpoint in managed code using Windbg

One of the great features of managed code is getting call stacks and proper class and member function names without debug symbols. We can examine the methods of a class and set breakpoints based on name. To see the methods on an object in Windbg we first
Posted by Kristoffer | 2 Comments
Filed under:
 
Page view tracker