Intel® Fortran Compiler
Build applications that can scale for the future with optimized code designed for Intel® Xeon® and compatible processors.
Announcements
FPGA community forums and blogs have moved to the Altera Community. Existing Intel Community members can sign in with their current credentials.
29306 Discussions

Debug question

dondilworth
New Contributor II
‎05-20-2012 03:52 AM
602 Views
Solved Jump to solution
When my program encounters an array index that is out of bounds, I want to see where in the code it happens. The debugger stops execution, but the call stack has only Windows routines, not my own subroutines. How can I get it to point to the error in my Fortran code?
0 Kudos
1 Solution
Anonymous66
Valued Contributor I
‎05-21-2012 07:47 AM
602 Views
Solved Jump to solution
To see where the error is occurring in your code, the option /traceback needs to be set. If you are using Visual Studio, it is under properties > Run-time > Generate Traceback Information. It is on by default in debug mode.

Annalee
Intel Developer Support

View solution in original post

0 Kudos
Copy link

Link Copied

1 Reply
Anonymous66
Valued Contributor I
‎05-21-2012 07:47 AM
603 Views
Solved Jump to solution
To see where the error is occurring in your code, the option /traceback needs to be set. If you are using Visual Studio, it is under properties > Run-time > Generate Traceback Information. It is on by default in debug mode.

Annalee
Intel Developer Support
0 Kudos
Copy link
Reply

Community support is provided Monday to Friday. Other contact methods are available here.

Intel does not verify all solutions, including but not limited to any file transfers that may appear in this community. Accordingly, Intel disclaims all express and implied warranties, including without limitation, the implied warranties of merchantability, fitness for a particular purpose, and non-infringement, as well as any warranty arising from course of performance, course of dealing, or usage in trade.

For more complete information about compiler optimizations, see our Optimization Notice.