Intel® Fortran Compiler 16.0 User and Reference Guide
If your program encounters a signal (exception) at run time, you may want to recompile and relink with certain command-line options before debugging the cause. The following will make it easier to debug the program:
Use the fpe[:]n option to control the handling of floating point exceptions.
To generate sufficient symbol table information and debug unoptimized code, as with other debugging tasks, use the -g (Linux* OS and OS X*) or /debug:full (Windows* OS) compiler option.
You can request that the program always stop when a certain type of exception occurs. Because certain exceptions are caught by default by the Intel® Fortran run-time library, your program stops in the run-time library code. In most cases, you want the program to stop in your program's source code instead.
To change how an exception is handled in the Microsoft debugger:
In the Debug menu, select Exceptions.
View the displayed exceptions.
Select Windows Exceptions. Select each type of exception to be changed and change its handling using the radio buttons.
Start program execution using Start in the Debug menu.
When the exception occurs, you can now view the source line being executed, examine current variable values, execute the next instruction, and so on, to help you better understand that part of your program.
After you locate the error and correct the program, consider whether you want to reset the appropriate type of exception to "Use Parent Setting" before you debug the program again.
For machine exceptions, you can use the just-in-time debugging feature to debug your programs as they run outside of the visual development environment. To do this, set the following items:
In Tools > Options, select Native in the Debugging Just-In Time category.
Set the FOR_IGNORE_EXCEPTIONS, as listed in Supported Environment Variables, to TRUE.