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

-save, debugger, <no value>

oh_moose
Beginner
‎01-14-2008 01:10 PM
443 Views
It seems the debugger (idb) cannot access any of the variables in a program if the program was compiled with the option -save. This does not explain the occasional loss of variable access posted in a prior message. With -save the debugger cannot access any of the variables anymore.

ifort -save -O0 -g -o a.exe a.for
Any trivial test program will illustrate the problem.

idb on IA-32, Version 10.1-32, Build 20070828
ifort on IA-32, Version 10.1, Build 20070913

Please do not ask me why I have to deal with libraries which need this option. smiley [:-)]

0 Kudos

Link Copied

1 Reply
Steven_L_Intel1
Employee
‎01-14-2008 01:56 PM
443 Views
Very odd. Please report this to Intel Premier Support and attach a test case.
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.