Troubleshooting: Kernel Profiler Does Not Collect Data (Windows CE 5.0)
Description
When run, the kernel profiler collects no data.
Resolution
Verify that you enabled profiling by setting the IMGPROFILER environment variable before building the run-time image. For more information, see Building a Run-Time Image That Supports the Kernel Profiler.
In the Config.bib file, verify that if the IMGPROFILER environment variable is set, PROFILE=ON.
For Monte Carlo profiling, verify that the OAL implements an interrupt for the kernel profiler. For more information, see Setting Up Monte Carlo Profiling.
Verify that the kernel profiler started and stopped when you instructed it to start and stop. The kernel profiler cannot start if, for example, you use keyboard shortcuts to control the kernel profiler with a keyboard driver does not support the kernel profiler. To verify that the kernel profiler starts and stops, you can use the debugger to insert breakpoints into the XXX_ProfileStart and XXX_ProfileStop wrappers in the Coredll.dll module. Alternatively, you can use a Debug build of the kernel, which prints output when the kernel profiler starts.
Note When you run the kernel profiler without KITL, the output of the kernel profiler is written to the same place that debug output is written. Typically, debug output is written to the debug serial port.
See Also
Setting Up the Kernel Profiler | Creating a Kernprof Version of the Kernel | Kernel Profiler Modes
Send Feedback on this topic to the authors