kaze
kaze

Reputation: 4359

Visual studio 2008 crashes when starting to debug

When I press F5, everything compiles fine, but when the app is to be started, VS crashes, showing the "Just in time debugger" dialog.

More than one (similar) solution has this problem. A new solution containing just a form, works. This problem started out of the blue, I have made no changes to the environment as far as I can understand.

I can start the app without debugging (ctrl+F5), and then attach the debugger.

I'm using VS 2008 sp 1.

Upvotes: 7

Views: 7371

Answers (7)

Cristian Popa
Cristian Popa

Reputation: 1

This happened to me just now, after my computer rebooted itself last night. When I was pressing F5 the app started but instantly shut down and the VS IDE crashed. To fix it: Debug->Delete All Breakpoints. It worked for me.

Upvotes: 0

Martha
Martha

Reputation: 1

I had the same problem, out of the blue the IDE would crash when I started to debug. Happened with any existing project that I opened, even the visual studio samples. I created a new project, just a blank dialog, ran it, and all was good. After that, the problem went away and I was able to debug again.

Upvotes: 0

Uvw
Uvw

Reputation:

If you have undocked windows in debug layout search KB960075 on code.msdn.microsoft.com (can't add hrefs).

Upvotes: 0

Nick Berardi
Nick Berardi

Reputation: 54854

Never seen this issue, have you tried turning off all your plug-ins like reSharper, CodeRush, etc.?


Update: When worst comes to worst I usually try this command line.

devenv.exe /ResetSettings
devenv.exe /ResetSkipPkgs 
devenv.exe /Setup

try all these you can do them all at once or do them individually it is up to you. But be aware that you will be deleting all your settings that you have customized in to Visual Studio, so you may want to back them up.

The last thing you can try is this, to see if the problem is with something weird that is running.

devenv.exe /SafeMode

Starts Visual Studio in safe mode, and loads only the default environment and services, and shipped versions of third-party packages.

Upvotes: 9

kaze
kaze

Reputation: 4359

I've found the problem now. I had "Step framework source" enabled, which somehow broke the debugger (strange though, because it usually works). Turning that off, made me debug as usual again.

Upvotes: 3

Ada
Ada

Reputation: 57

try repair or reinstall, don't waste time findin' the reason of the problem

Upvotes: 0

David Robbins
David Robbins

Reputation: 10046

Do you have CLI.exe error issues? Check your event log. I've had the same issue and simply re-staged my machine out of panic since I was so near a deadline. I assumed that it was an issue with the registry and couldn't find an answer.

Upvotes: 0

Related Questions