Kristoffer's tidbits

Bits and pieces of useful information by Kristoffer Henriksson

Browse by Tags

Tagged Content List
  • Blog Post: 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 for a while to determine why after 12 hours memory...
  • Blog Post: 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 to still be useful. For my test scenario I have...
  • Blog Post: 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 a CLR exception and pops into the debugger....
  • Blog Post: 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 need to find its method table. We can do this...
  • Blog Post: Getting started with Windbg and managed code

    Windbg (or wind bag as my friend calls it) is my one stop shop for almost everything debugging related. It's great for finding issues that only happen on a client machine and you don't want a full blown Visual Studio installation mucking up your repro. With the sos extension Windbg becomes useful at...
Page 1 of 1 (5 items)