If broken it is, fix it you should

Using the powers of the debugger to solve the problems of the world - and a bag of chips    by Tess Ferrandez, ASP.NET Escalation Engineer (Microsoft)

December, 2005

  • If broken it is, fix it you should

    Things to ignore when debugging an ASP.NET hang

    When looking at a dump, a lot of the art of debugging (I like to call it an art because it makes me feel more important:)) is knowing what you can ignore so you can get to the goodies. Especially if you are looking at a hang, it’s nice to know what the most common threads are so you can just scan them and say not that one, not that one, well you get the idea. Since I work mostly with asp.net I’m going to dissect a w3wp.exe dump (IIS 6) and show you some of the more common stacks. Common for...
  • If broken it is, fix it you should

    Associate windbg with .dmp files

    If you get tired of starting the debugger, loading your dump, setting up your sympath, loading your extensions, etc. etc. here is a nifty way of getting "Debug this dump" on the context menu for .dmp files and get all your favourite commands automatically loaded. First create a .reg file with the following contents (as always be very careful when modifying the registry) Windows Registry Editor Version 5.00 [HKEY_CLASSES_ROOT\.dmp] @="Debugger.Dump" [HKEY_CLASSES_ROOT\Debugger.Dump] ...
  • If broken it is, fix it you should

    Why do I get weird function names on my stack? (a discussion on symbols)

    Symbols can contain information about global variables, local variables, function names, parameters, structures and source line numbers. There are 3 types of symbols, export symbols, pdb symbols (public symbols) and private pdb symbols (private symbols). The export symbols are part of the dll itself. For example ntdll.dll and kernel32.dll expose a big part of their functions as export symbols so that they can be called as API’s, but most dll’s that you find in a process have a very small set...
Page 1 of 1 (3 items)