Is there somethingabout using /optimize:2 /fpe:0 and using a full-debug mode? I am using v10.0.025 on Win64 with VS2005.
The proram runs successfully with the following combinations:
(2) /optmize:2 and full debug
(3) /optimize:0, full debug, and /fpe:0
I use /traceback /check:uninit /check:bounds.
When I use /optimize:2, full debug, and /fpe:0 I see one variable getting a value NaN. This variable is not used in any calculation relevant to the problem and I can see the code that initializes this variable to zero. In fact, in theproblematic configuation, the variable gets NaN exactly when the code is trying to initialize it to zero. The resulting NaN changes the values of variables computed earlier and the program diverges. I see the NaN only by using the breakpoints. The program does not throw an exception.
I believe the above symptoms are that of a memory stomp; but it seems to extremely difficult to see where. Any suggestions?