4

Visual Studio is the worst. Ever. I was about a half hour digging into debugging my code, and I was about 8 layers deep into the API, with breakpoints to anchor me to each level. With no warning, Visual Studio crashed and I lost all my breakpoints, and I didn't know which file I left off in. I had to completely restart the debugging process. Visual Studio deserves to burn...

Comments
  • 2
    Tip, for deep debugs try trace points that write to the interactive console.

    Those are less likely to crash.

    Had the same problem with a deep recursive function that sometimes got a 200 level deep stacktrace which almost always broke the debugger.

    And no, due to the problem it solves its not very easy to reduce the stack depth.

    I believe it can be done but will require extensive refactoring of some very complex code.

    Another day ...
  • 0
    @apisarenco Working and a large company, even if there was another IDE that worked, I couldn't use it
Add Comment