I do not believe that this is a bug in ifx, rather a bug (aka feature) in MS VS.
Consider the following screenshot:
The program crashed at the line of the arrow due to the unit for READ was 0.
Note, at this point in execution (and by inspection) SEContext%useWaypoints == .false.
Therefor, the execution should never entered this if section (top line of screen shot)
Oddities, on the second line there is a "pin" with: "vIntegrationStepsize pinned to line 1350"
How that got there I haven't a clue. I was able to remove this with right-click.
What I am asking is would pinning a variable to a source code line alter the runtime code?
If not, I am at a loss to explain how I entered this section of code.
Other than corrupting the return address on stack, I cannot see how this section of code could be entered....
... other than a really old MS VS bug.
Many years ago (~15?) I encountered a problem with breakpoints. Where the break instruction (INT03) was inserted into the code into the middle of an instruction sequence (i.e. not as the 1st byte of the instruction). The odd part was that no break point was set near this position. This was symptomatic of the MS VS internal table of where to place the breakpoints got corrupted. The only way to clear this was to use the "clear all breakpoints" (note, clearing them one at a time does not work).
If anyone else runs into something similar, try the "clear all breakpoints" but report here that you had a similar problem.
Jim Dempsey
Link Copied
