-save, debugger, <no value>

-save, debugger, <no value>

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.

2 posts / 0 new
Last post
For more complete information about compiler optimizations, see our Optimization Notice.

Very odd. Please report this to Intel Premier Support and attach a test case.

Retired 12/31/2016

Leave a Comment

Please sign in to add a comment. Not a member? Join today