gtpp1m1e | Program Development Support Reference |
Use C function trace to trace ISO-C programs that have been compiled using the TEST compiler option of one of the IBM C/370 family of compilers supported by the TPF 4.1 system. C function trace provides relevant information to help analyze C program problems, therefore reducing the development cycle of these C programs.
C function trace uses breakpoints generated by the compiler when a program is compiled using the TEST compiler option. Breakpoints are grouped into types, for example, program entry, program exit, and others. The default values of these breakpoints are no-operation instructions.
If the C function trace of program entry breakpoints and program exit breakpoints is enabled by specifying the CDEBUG parameter on the ZSTRC command or by specifying the ENTRY and EXIT parameters on the ENATC macro, the program entry breakpoints and the program exit breakpoints are modified so that the C function trace is run.
If the C function trace of breakpoints other than program entry breakpoints and program exit breakpoints is enabled by specifying the CDEBUG and XHOOKS parameters on the ZSTRC command or by specifying the OTHERS parameter on the ENATC macro, the other breakpoints are modified so that the C function trace is run for these breakpoints.
The trace environment is established when:
The major elements of the C function trace environment are:
See Controlling Traces for more information about how these elements are set up and controlled.
C function trace provides trace information for each ECB, for:
When C function trace is active, each ECB that invokes C functions has its own C function trace table. Once the trace is started, subsequent attempts to alter or reset the trace environment have no effect on the currently running ECB. However, you can stop and start C function trace at any time using the ENATC macro.