PocketBuilder provides three ways to analyze trace information using built-in system objects and functions:
Analyze performance by building a call graph model
A 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 model
A 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. No matter which way you analyze trace files, you can analyze them on the desktop only—the profiling functions are not supported on deployment devices.
Supporting files needed
To create a profile from a trace file, PocketBuilder must
also access the PKL, PKD, or
executable file used to create the trace file. If you create the
trace file on a handheld device, you must copy the trace file and
the executable file to the desktop. The PKL and
PKD files must also be available on the desktop.
