Debugger looses track of code lines

[habbink]

Sometimes the debugger seems to lose track of the proper code lines. It will for instance step to a comment line or mis a breakpoint because it "thinks" it's somewhere else. I'm using IVF 9.0 and Visual Studio .Net vsn. 7.1

[TimP]

Yes, I have complained about a similar problem. If you use IPO, you could have such problems in in-lined subroutines. Beyond that, unfortunately, the answer given me is that Microsoft does not permit 3rd party compilers to use the most reliable and up to date methods for generating .pdb.
Splitting the source into as many separate compilations as possible can help, at least by minimizing the regions which exhibit the problem, and by preventing IPO. Reducing optimization, to -O1 or -Od, could make a difference.
If you could submit a problem report on premier.intel.com, at least you would help document that there is a problem here.

[jimdempseyatthecove]

I've been fighting this issue for years. But I will say that improvements have been made over these years. Preprocessed source files used to have substantial problems, this is mostely fixed now.

Some times I have to resort to opening up the Disassembly window and ignore the misplaced comments (.f90 source code). Usualy there is enough information in the disassembly window to figure out where you are.

If the line numbers at the beginingof the subroutine being debugged are goofed up then place the break point on the subroutine statement itself. On break, open the Dissassembly window and step through from there.

It is a P.I.A., but at least you are not dead in the water - so to speak.

Jim Dempsey