To diagnose a program source file, filnam, simply enter: d filnam.
Or, use abbreviation: d, d1...d10, to diagnose the previously diagnosed file, the file in the n'th box under subtitle: DIAGNOSE, respectively.
Then select from the menu, or type in the subroutine you want to diagnose.
The diagnoser will set up the subroutines/program that may contain the bug by recompiling them, such that the next time you run the program, the execution will be tracked by variables, line-by-line, or subroutine.
But this process has been automated such that, if all goes well, the diagnoser would automatically bring you to editting the troubled statement, inside the troubled subroutine, and all ready to be submitted and executed again.
There is also 3 levels of background tracking of the execution, if you click the Track option on the upper left corner of the screen.
In the case of the editor, we can also take advantage of the robot file that keeps a log of all the commands issued. In this robot file, we could also write in all the debugging statements, and when intermingled within the sequences of editting command, it gives a clear picture of what's going on under the hood.
Click to learn about:
TRANSLATOR
RECORDER
OUTERNET
EDITOR HOW
USER INTEFACE
2.7
OUTERNET
2.11
FORTRAN SPECS
2.12
USE INTERFACE SPECS
2.13
EDITOR SPECS
2.14
DIAGNOSER SPECS
2.15
DATA FILE LINK SPECS
2.17
UNIVERSAL LANGUAGE FOR COMPUTING