• greggm's WebLog

    Debugging Classic ASP Code

    • 6 Comments
    Since shipping Visual Studio 2005, we have heard from some users complaining about the fact the Visual Studio 2005 doesn’t support debugging classic ASP code. Today I want to talk about what we recommend you do to debug your ASP code. Visual Studio...
  • greggm's WebLog

    Inside 'Image File Execution Options' debugging

    • 16 Comments
    There are times that you need to debug the startup code for an application, but something else is launching the application. Classic examples might be services or setup custom actions. Luckily, the OS team came up with a way to debug these problems: ...
  • greggm's WebLog

    Disabling script debugging in VS 2008 + IE8

    • 8 Comments
    Visual Studio 2008 shipped with a feature to automatically enable script debugging when starting IE8 from Visual Studio. In other words, if you are using VS 2008 and IE8, there is no longer a need to tweak IE options to debug your site. However, this...
  • greggm's WebLog

    Explaining 'The Binding Handle Is Invalid'

    • 14 Comments
    Today I want to try to give more insight into the 'Binding Handle Is Invalid' problem that a number of people have reported with the VS 2005 debugger. First, if all you care about is how to solve the problem: Enable the 'Terminal Services' service...
  • greggm's WebLog

    Diagnosing 'The debugger is not properly installed'

    • 58 Comments
    One of the error codes that we included in the VS.NET 2002 and 2003 debuggers is: The debugger is not properly installed. Run setup to install or repair the debugger. Diagnosing this is much harder then it should be (more on this later). For now lets...
  • greggm's WebLog

    Func eval and System.Windows.Forms.Form

    • 7 Comments
    If you ever try to debug a multi-threaded Windows Forms application, today's blog is for you. A customer asked me about this issue, and since I have also run into this problem, I decided to talk about it. What is func eval? If you already...
  • greggm's WebLog

    Remote Debugging without domain accounts

    • 7 Comments
    This blog has been on my todo list forever. I am now sitting in an airport, so I guess it is time for the procrastination is over… I want to talk about remote debugging in the following network situations: Two domains without two-way trust Two computers...
  • greggm's WebLog

    How script debugging works

    • 2 Comments
    There are a couple of players in client side script debugging: Script host (example: wscript.exe, mshtml.dll or asp.dll). This is the application that wants to run script. The host is responsible for giving the text of documents to the debugger...
  • greggm's WebLog

    Configuring XP SP2 to enable remote debugging for VS 2002/2003

    • 8 Comments
    Soon we will get the remote debugger KB article fixed, and this blog will be useless. In the mean time… Basic steps to get remote debugging to work after installing XP SP2: Configure DCOM on the Visual Studio computer Configure Windows Firewall on both...
  • greggm's WebLog

    Debugging Windows Error Reporting

    • 3 Comments
    If you’re a software developer, chances are that you have written an application, and this application has crashed. When this happened, it probably put up a dialog that looks something like this: How do you figure out what went wrong? Strategy...
  • greggm's WebLog

    Debugging an ASP.NET application as a non-admin

    • 15 Comments
    The debugger team has gotten many requests to debug ASP.NET applications as a non-admin. In Whidbey, the ASP.NET team did a good job solving this problem. Their solution is much nicer then mine. In the mean time, here is a way that you can get this scenario...
  • greggm's WebLog

    Interop debugging and mscorwks.pdb

    • 1 Comments
    If you are doing interop debugging (managed+native debugging), I strongly recommend that you have symbols for mscorwks.dll. Interop debugging requires the debugger to walk the stack through stubs from mscorwks.dll, and without symbols, the debugger is...
  • greggm's WebLog

    Debugging WCF Services in Visual Studio 2008

    • 1 Comments
    One of the new features that we added in Visual Studio 2008 was debugger enhancement for Windows Communication Foundation (WCF) services. There are four features that we support: You can step from a service client into the implementation. Just...
  • greggm's WebLog

    Fixing 'You do not have permissions to debug the server' errors

    • 10 Comments
    First, some background. The way we start ASP.NET debugging is to send a special request to ASP.NET over HTTP/HTTPS. The verb for this request is 'DEBUG'. If everything goes as planned, this allows VS to know what process to attach to. Displaying error...
  • greggm's WebLog

    Setting conditional breakpoints using object ids

    • 15 Comments
    In native code, its sometimes useful to set a breakpoint condition so that a breakpoint will only stop for a particular instance of an object. To do this, I simply use the address of the object: this == (CMyObject*)0x10fc10 In managed code, the...
  • greggm's WebLog

    Retail code debugging

    • 7 Comments
    Retail code debugging is one of those necessary evils. It's difficult, but the only way to completely avoid it is to not have retail code, which unfortunately usually requires you to avoid having any customers. Anyway, I figured I would give a brief tour...
  • greggm's WebLog

    Data Breakpoints

    • 8 Comments
    Usually, people put breakpoints on an instruction. These breakpoints are set by replacing the first byte of an instruction with the ‘int 3’ instruction (0xcc). When the processor executes the ‘int 3’ instruction, it causes the...
  • greggm's WebLog

    Script debugging tips

    • 5 Comments
    Monica wrote a very nice document for this feature. A few quick highlights: Internet explorer defaults to having script debugging disabled. IE also likes to disable script debugging when you install a new version of IE (example: XP SP2). In IE, go to...
  • greggm's WebLog

    Breaking when a module loads

    • 6 Comments
    We occasionally get requests for the ability to break when a module loads. WinDbg (the other debugger that Microsoft produces) exposes this as an exception (see the 'sx' command), although it isn't really an exception. Ideally, I think this should be...
  • greggm's WebLog

    Windows Vista: User Account Control and the Debugger

    • 3 Comments
    As far as the debugger is concerned, the biggest feature in Windows Vista is user account control. You can read all about it on technet -- but the basic idea is that even if you are an administrator on your computer, your programs normally run without...
  • greggm's WebLog

    A debugging tale

    • 5 Comments
    In my opinion, one of the best feelings in life is when you finally solve a great bug. I have a hyper-focus personality, so I really hate it when I have to go home with my problem unsolved. I have a really hard time not thinking about it. For six days...
  • greggm's WebLog

    Hints on using Just-In-Time debugging with Windows Vista

    • 1 Comments
    Just-In-Time debugging is trickier on Windows Vista than on previous operating systems. Today I am going to talk about the various knobs that you can use to make this better. Hint #1 : Use Visual Studio 2008 Beta2. I expect Beta2 to be out soon. If...
  • greggm's WebLog

    Debugging a .NET Framework 2.0/3.0/3.5 class library with VS 2010

    • 2 Comments
    A number of people have had difficulty debugging a .NET Framework 2.0/3.0/3.5 class library that loads into a native executable. The debugger will launch, and their code will run, but the debugger will not stop at breakpoints, detect that modules load...
  • greggm's WebLog

    How to find the owner of a critical section

    • 4 Comments
    Many times in my life I have needed to debug a deadlock. You have one thread trying to acquire a critical section, and it can be a pain to determine which thread has it. Setup: Go get OS Symbols. Having OS symbols is a must, and will make your life...
  • greggm's WebLog

    Breakpoint exceptions from the heap

    • 2 Comments
    New programmers sometimes ask why the debugger stopped at a ‘user breakpoint’ exception in their program. The exception dialog will come up and say something like: Unhandled exception at 0x77f75a58 in CoruptHeap.exe: User breakpoint. ...
Page 1 of 5 (114 items) 12345