Visual Studio 2005 Debugger crashes

[emonette123]

I currently use VS 2005 SP1 and Intel Fortran Compiler Integration 9.1.3192.2005.

I often experience crashes when I debug code. Not only me, it also happens to one of my collegues. The debugger will crash, telling Microsoft Visual Studio has encountered an internal error. The you get the Send Report button. It will crash when you step the code or when you step into.

Anyone experienced this? It is pretty annoying. You have to close Visual Studio and start again, not knowing when your F10 hit will be your last one.

Thanks,

Etienne

[Antoon]

Hi,

Yeah, that's also my experience, lot of crashes each day popping up with an error windowif you want to send an error report. In some way you get used to everything. The previous IDE, Microsoft Visual C++ 6.0 with Compaq Fortran compiler was much more stable than VS2005 SP1, for sure !

Are there new releases (SP2 ?) including all thosebugfixes planned for near future?

Antoon

[Les_Neilson]

Quoting - emonette123

I currently use VS 2005 SP1 and Intel Fortran Compiler Integration 9.1.3192.2005.

I often experience crashes when I debug code. Not only me, it also happens to one of my collegues. The debugger will crash, telling Microsoft Visual Studio has encountered an internal error. The you get the Send Report button. It will crash when you step the code or when you step into.

Anyone experienced this? It is pretty annoying. You have to close Visual Studio and start again, not knowing when your F10 hit will be your last one.

Thanks,

Etienne

This is almost a FAQ on the forum. It happened in VS2003 and2005. We have just recently upgraded to VS2008 and I'mwaiting to see if it still occurs. Clicking "Send report to Microsoft" seems to have no effect - perhaps their spam filter eats it.

There was amention of this problem by myself and Jim Dempsey back in January 2008
see : "Mysterious run time error with IVF 9.0"
http://software.intel.com/en-us/forums/showthread.php?t=56797

See especially Jim's analysis of the problem (reply number 8 in the thread)

Les

[emonette123]

Quoting - Les Neilson

This is almost a FAQ on the forum. It happened in VS2003 and2005. We have just recently upgraded to VS2008 and I'mwaiting to see if it still occurs. Clicking "Send report to Microsoft" seems to have no effect - perhaps their spam filter eats it.

There was amention of this problem by myself and Jim Dempsey back in January 2008
see : "Mysterious run time error with IVF 9.0"
http://software.intel.com/en-us/forums/showthread.php?t=56797

See especially Jim's analysis of the problem (reply number 8 in the thread)

Les

Thanks for your answer Les, sadly though it tells me there is no cure to my problem...

What I experience is different from topic 56797. I do not build inside Visual Studio, I only use it for debugging, opening the executable as a project. So it has nothing to do with Stack size. And, for what I know, the executable I debug does not have weird bugs in it.

It is a very tricky bug. It will not crash when I start debugging, it will crash during a debug session. So I doubt this is a question of a race condition between some saving of the session. I will be able to go more or less further if I use different combination of run to break point and step or step into, but eventually, it will crash. And it doesn't crash at the same program location each time.

Very annoying, never happened in VC 6.0.

Etienne

[jimdempseyatthecove]

Etienne,

Some additional information related to my experiences.

These problems are not occuring now, but when they were they were rather baffeling. Scenarios of wierd debug sessions:

Scenario 1: Start debugging session, get going on debug session for several minutes to get to the point of a problem only to get on the break point a "We're sorry,... we will have to restart Visual Studio..." typically with the error writing to somewhere near location 0. No code executed by the application was responsible for the error.

Scenario 2: Unable to F5 to start debug session. Unable to set break point on first statement of program and issue F5 or Debug | run.
*** However, if I would (from IDE) issue Step Into, to get to the C Runtime System startup code, and open the Dissassembly window and place a break at the call to the program main (or step through the startup code to find the call to main/winmain). Then when at break simply wait for 15 seconds, then Continue the debug session worked.

It sounds like your problem is scenario 2 (although you are not starting from the IDE). Try stepping into your C Runtime System startup code, then wait just before the call to your main.

Stranger than fiction. Wouldn't you say?

What I had accidentally found out about a work around was if you recreate your solution and project files the problem goes away for some time. Why this is so, I haven't a clue. In my case this was about 13 projects with 750 files. A non-trivial amount of time.

Good luck in finding your work around

Jim Dempsey

[Steve_Nuchia]

This is probably not the problem described but it's something to watch out for:

https://connect.microsoft.com/VisualStudio/feedback/ViewFeedback.aspx?FeedbackID=377121

[emonette123]

My problem is problem number 1)

I am always able to start the debugger, the crash occurs when I step the code. But it doesn't always crash at the same spot. It also happened to me it was in such a bad state it crashed during the program execution... Ugly. And I am still looking for a work around. Usually, using the same model, but with a slightly different version of the executable will produce less or no crash at all.

Regards,

Etienne

[misunderestimated]

Quoting - emonette12

I currently use VS 2005 SP1 and Intel Fortran Compiler Integration 9.1.3192.2005.

I often experience crashes when I debug code. Not only me, it also happens to one of my collegues. The debugger will crash, telling Microsoft Visual Studio has encountered an internal error. The you get the Send Report button. It will crash when you step the code or when you step into.

Anyone experienced this? It is pretty annoying. You have to close Visual Studio and start again, not knowing when your F10 hit will be your last one.

Thanks,

Etienne

[misunderestimated]

Quoting - misunderestimated

Sorry I hit the wrong botton in my first try. Anyway, I am doing mixed VC++ 2005 and Compaq Fortran programming. Things had been working fine before yesterday when the VS debugger crashed repeatedly at the location where a Fortran subroutine was called. After pulling half of my hair off trying to figure out what went wrong, I decided to clear all the old break points. The problem went away!