Analyzing trace information programmatically
PowerBuilder provides three ways to analyze trace information
using built-in system objects and functions:
-
Analyze performance
by building a call graph modelA call graph model contains information about all the routines
in the trace file: how many times each routine was called, which
routines called it and which routines it called, and the execution
time taken by the routine itself and any routines it called. -
Analyze program structure and logical flow by building
a trace tree modelA trace tree model contains information about all recorded
activities in the trace file in chronological order, with the elapsed
time for each activity. -
Access the data in the trace file directly
Trace objects and functions let you build your own model and
analysis tools by giving you access to all the data in the trace
file.
The profiling tools use the first two ways. The Class and
Routine views are based on a call graph model, and the Trace view
is based on a trace tree model.
Supporting files needed
To create a profile from a trace file, PowerBuilder must also
access the PBL, PBD, or executable
file used to create the trace file, and the PBL,
PBD, or executable file must be in the same location as when the
trace file was created.