Debugging problem

[tiho]

Hi

Myprogram gets into a crash and the debugger doesn't give any information about the crash. On the black screen I get the error message

forrtl: error (72): floating overflow
Image PC Routine Line Source
inteldev.exe 030FCF26 Unknown Unknown Unknown

In the callstack

IntelDev.exe!_control87(unsigned int newctrl=196608, unsigned int mask=0) + 0x6C
IntelDev.exe!_controlfp(unsigned int newctrl=196608, unsigned int mask=0) + 0x15C
IntelDev.exe!_for__nt_handler_jacket.() + 0x95C
IntelDev.exe!_for__nt_handler_jacket.() + 0x35C
IntelDev.exe!_main() + 0xdeC
IntelDev.exe!mainCRTStartup() Line 259 + 0x19C
kernel32.dll!7c816fd7()
ntdll.dll!7c915b4f()

The debugger opens the file crt0.c which is some kind of C initialization file as far as I can see. Nothing though points to which of my code line caused the crash. This problem started occurring lately for every crash so it's not just a particular code segment that is problematic. I suppose some of the compiler options may be responsible for this. Any ideas for how to fix the problem?

Thanks a lot in advance.

Tihomir

[Steven_L_Intel1]

Is this a Release mode build? I would expect that if you built this as a Debug configuration and started it in the debugger you would see it stop at the point of error.

You probably have also changed the "Floating Point Exception" option from the default of /fpe:3 to /fpe:0 as otherwise you would get "Infinity" in results rather than an overflow error. (Though personally I'd rather see the error.)

[tiho]

Thanks Steve.

I am running this in Debug mode with these compiler options

/Zi /fpscomp:ioformat /Qauto /module:"$(INTDIR)/" /object:"$(INTDIR)/" /c

I did try /fpe:0 recently but since then I have turned that option off and is now at the default. I also tried adding /fpe:3 to the command line but that didn't fix the problem either.

Thanks

Tihomir

[Steven_L_Intel1]

I'm puzzled that /traceback is not among the default options. Are you building in Visual Studio? What happens when you start this program in the debugger, rather than debugging after the error? What version of the compiler are you using?

[tiho]

Steve

Actually the raceback was in there. Here again the Compiler command line:

/Zi /Od /fpscomp:ioformat /Qauto /module:"$(INTDIR)/" /object:"$(INTDIR)/" /traceback /c

I am using Visual Studio. I can start the program in the debugger, the program crashes after about 10000 lines of code, butthe debuggerdoesn't say which line. Most of the time this happens when an array has been deallocated and consequently has been accessed.

The compiler version is 9.1.032, the debugger version is 9.1-25.

Thank you.

Tihomir

[Steven_L_Intel1]

At this point I would suggest sending a test case to Intel Premier Support.