This routine was (until I fixed it) was generating a breakpoint when it read a line from LGU 3.
It did tell me where the breakpoint was in the output file, but the debug arrow pointed to somewhere else in the program
that didn't even any I/O statements. In fact it pointed to the END of a routine that had nothing to do with this one at all.
also when it generates the breakpoint, it will not identify any symbols within this routine when I put the cursor on them.
Apparently the debugger does not generate the correct info regarding WHERE the breakpoint occurred, even though
the output file DOES have the correct information.
Any clues as to why this might occur? Apparently the interaction between the I/O library and the debugger is messed up.
If I need to upload the whole program to isolate this, I can do so.
| Attachment | Size |
|---|---|
Download uscram.f90 | 935 bytes |