Arrays largely present incorrect sizes. The commonest error is exhibiting an array measurement of 1:0. Right here I simply stepped over these assignments and tried to view the array:

In one other copy of VS I had operating on an analogous exe, I acquired:

Each incorrect for the reason that array contactPoint_dif is asserted as measurement 2. It is not an allocatable. You cant even try and entry a component utilizing the watch window because it falsely detects index out of vary.

Are we anticipated to dot our code with print statements on the console to see the numbers ? That is what I’ve to do for hours. Intel’s debugger is the primary cause we’re ditching Intel compilers.

That is all utilizing newest Visible Studio and newest compiler and debugger on Home windows.

Undertaking configuration is Debug. No I cant present the code and its unlikely I may present made up code to copy the difficulty. However that is no excuse. You need to have some massive initiatives of your personal.

Right here is the compile command line:
/nologo /debug:full /MP /Od /fpp /I”..IMSLemt64″ /I”..AdditionalLibsDebugx64″ /I”D:DevrxsstaticscalculatorMSXMLInterfacex64Debug” /I”D:DevrxsstaticscalculatorUtilitiesx64Debug” /I”D:DevrxsstaticscalculatorDifferentialMathsx64Debug” /I”D:DevrxsstaticscalculatorDataPackagex64Debug” /I”D:DevrxsstaticscalculatorBearingDatax64Debug” /I”D:DevrxsstaticscalculatorMathsConstantsx64Debug” /I”D:DevrxsstaticscalculatorCustomStaticsCouplingx64Debug” /DINITNAN /DDEBUGV /Dx64 /DenhancedChecking /DenableIMSL /assume:recursion /Qopenmp /standard-semantics /warn:declarations /warn:unused /Qinit:snan /module:”x64Debug” /object:”x64Debug” /Fd”x64Debugvc170.pdb” /traceback /test:pointer /test:bounds /test:form /test:uninit /test:format /test:output_conversion /test:stack /libs:dll /threads /dbglibs /Qmkl:parallel /c