Intel® Fortran Compiler
Build applications that can scale for the future with optimized code designed for Intel® Xeon® and compatible processors.

Where has the "traceback" gone?

NH_Veldhuijzen
Beginner
6,847 Views
Dear all,

I'm always using the "-traceback" option, so I can see immediately where to look for errors in my source file (because the number of the offending line in the source file is shown). Now I'm using IVF11.1.065 and, although the option is still on, line numbers are no longere present in the error message. Does anyone have a suggestion as to how to have these line numbers back in the error message? (I cannot look in the help files; seee my other post to this forum.)
0 Kudos
24 Replies
mikegor
Beginner
610 Views
But maybe it will be possible to issue a sort of hotfix for the traceback problem? The tracebackfunction is very important for a developper.
0 Kudos
Wendy_Doerner__Intel
Valued Contributor I
610 Views
This thread will be updated as soon as we have compiler that resolves the issue. Thanks for the feedback.

------

Wendy

Attaching or including files in a post

0 Kudos
mikegor
Beginner
610 Views
This is how this looks like for Intel Visual Fortran Compiler XE 12.1.1.258:
0 Kudos
Martyn_C_Intel
Employee
610 Views

The fix for this issue was implemented in the version 13 compiler, That's a long time ago, sorry not to have posted at the time. I have  confirmed that /traceback works in conjunction with /check:all in the current version 15 and version 16 compilers. (/check:all causes optimization to be disabled if it's not already a debug build). /traceback itself, without /check, is designed to work also with optimization.

0 Kudos
Reply