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)

April, 2007

  • If broken it is, fix it you should

    .NET Garbage Collector PopQuiz - Followup

    It was really exciting to see that so many people answered the .NET GC PopQuiz , especially seeing that so many had great answers. Perhaps the questions were too easy:) The reason I posted the pop quiz in the first place is that, as opposed to Phil, who commented that none of this should really matter to the developer:), I do think that a good understanding of what happens behind the scenes when you are programming on top of a lot of code that you don't control, is important since it tells you...
  • If broken it is, fix it you should

    .NET Garbage Collection PopQuiz

    Time for a little pop-quiz/potential interview questions to get some action going in the comments section... Feel free to answer any or all of the below questions, I'll follow up with a post later if all of them are not answered... 1. How many GC threads do we have in a .NET process running the Server version of the GC on a dual-core machine? 2. What GC mode is used in the web development server (cassini) on a quad proc machine? Why? (you can choose from server, workstation or concurrent...
  • If broken it is, fix it you should

    Things to ignore when debugging an ASP.NET Hang - Update for .NET 2.0

    I often get questions like "what is this thread doing?". A lot of the time it is about threads that are essential to the process but completely unrelated to the problem at hand. A while back, in the beginnings of this blog, I wrote a post about what threads you can ignore so you can focus on what is important , and according to the blog stats, it turned out to be one of the most popular posts. Since then a lot of people have wanted to see an update for 2.0. Rather than repeating the whole post...
  • If broken it is, fix it you should

    WinDBG Scripts

    I see post-mortem debugging as: 39,5 % taking memory dumps at the right time 20,5 % running the same ol' commands over and over 31 % jumping to conclusions based on experience and proving the theory, and... 9 % pure luck, i.e. you happen to stumble upon something when poking around Don't you just love it when people apply arbitrary percentages to abstract things, especially here, 9% of what, and how did I get to that conclusion :) And have you noticed that as opposed to this list...
  • If broken it is, fix it you should

    Swedish .NET Debugging PodCast

    I know most of you probably don't know Swedish, but for those of you who do, here is a link to a podcast http://buzzfrog.blogs.com/zabrak/2007/04/av_91_tes... where Dag König is interviewing me about .NET issues and debugging. Laters, Tess
Page 1 of 1 (5 items)