Debugging TACL Programs
Developing TACL Programs
107365 Tandem Computers Incorporated
2–35
OTHERWISE ]
-TRACE-
-6-
[#CASE 1
^
-TRACE-
-6-
TEDIT [editfile]
^
-TRACE-
The user issues a DISPLAY command to see the contents of the variable EDITFILE and
sets a breakpoint on that variable:
-6-DISPLAY editfile
sect08
-7-BREAK editfile
The RESUME command terminates the debug mode, and processing continues until
the routine is ready to invoke EDITFILE, at which point the set breakpoint invokes
_DEBUGGER again, which displays the word -BREAK- to show why it was invoked:
-8-RESUME
TEDIT editfile
-BREAK-
The user displays the contents of EDITFILE again, clears the breakpoint, and resumes
normal processing:
-9-DISPLAY editfile
sect08
-10-CLEAR editfile
-11-RESUME
Control passes to TEDIT. After you exit,
the routine displays:
DONE WITH $VOL.SUBVOL.SECT08
To modify a variable during a debugging session, use the MODIFY command. After
entering the new value, press RETURN, then enter CTRL/Y to signify that there is no
more input. At prompt 10, in the previous example, you could type the following to
change the name of the edit file:
-10-MODIFY editfile
Input new contents of :EDITFILE.1; end with eof
-:EDITFILE.1-sect09
-:EDITFILE.1-EOF!
-11-D editfile
sect09
-12-
By using the MODIFY command, you can determine how a change affects the
program. You can also force choices based on variable values without having to
change the function and rerun it. For example, you can alter the contents of the text in
a #CASE function to force TACL to take a path that you want to test.