Code Profiling (Windows CE 5.0)
Remote Call Profiler begins recording profiling data when the OS loads the first instrumented module. Logging continues until the last process registered with the logger terminates.
With Remote Call Profiler, you can use the Collection Control window to control the amount of data collected during a profiling run.
In the Collection Control window, you can start and stop profiling during the profiling run. Alternatively, you can insert Remote Call Profiler data collection functions into your code before you compile the code.
You can use the data collection functions to specify where in the code to start and stop profiling.
Remote Call Profiler profiles 10 processes and 32 threads by default. For information about setting the number of processes and threads to profile, see Choosing the Number of Processes and Threads to Profile.
Note Remote Call Profiler does not collect data for fibers. When a thread converts to a fiber, data collection for the thread stops. Remote Call Profiler continues to collect data for other threads.
See Also
Data Collection Control | Target Device Rebooting | Data Viewing in Remote Call Profiler
Send Feedback on this topic to the authors