After you have created a trace file, the easiest way to analyze it is to use the profiling tools provided on the Tool tab of the New dialog box. There are three tools:
The Profiling Class View shows information about the objects that were used in the application
The Profiling Routine View shows information about all the routines (functions and events) that were used in the application
The Profiling Trace View shows the elapsed time taken by each activity in chronological order
Even if you want to develop your own analysis tools, using the profiling tools is a good way to learn about these models and about profiling in PocketBuilder. When you are ready to develop your own tools, see “Analyzing trace information programmatically” for an overview of the approaches you can take.
Viewing profiles from a handheld device
The profiling tools included with PocketBuilder work only
on the desktop. If you use the profiling tools to view a trace file
from a deployment device, you must copy the executable for the application
that created the trace file to a desktop directory. The desktop
directory must have the same path name—with the exception
of the initial drive letter—as the path where the executable resides
on the device. For example, for an application residing in the \Program Files\Tests
directory on a device, you must copy the executable to \Program
Files\Tests on the current drive on the desktop.
You must also copy the PKP trace file from the handheld device. Although you can copy the PKP file to any location on the desktop, when you select the PKP file in a profiling tool you also set the current drive; therefore you should copy the PKP file and the executable file to the same drive on the desktop.
