Kernel Tracker is a helpful tool included in eVC++ and Visual Studio for WindowsCE Development. It allows the developer to view the execution sequence of processes and threads in the system. Many developers use it to create a "profile" of their application when it is running, so as to identify bottlenecks and performance issues in the system or their application architecture.
Listed below are several helpful links regarding Kernel Tracker and how to use it.
Collecting Data On A Standalone Device With CeLogFlush Tutorial on how to collect CeLog data from a CE System without using ActiveSync. CeLogFlush.exe and CeLog.dll are used to capture data to a log file on the system which can then be opened with the Remote Kernel Tracker viewer. This allows log capturing during sleep and wake, which breaks an ActiveSync connection. This should only be done in a limited amount of time as the log file can grow quite large over several minutes.
Sue Loh's Blog Sue Loh's Blog is a great resource for many different CE Topics, but she presents several helpful posts throughout it on how she used Kernel Tracker to identify certain hard to spot problems. These are very helpful in learning how to use Kernel Tracker effectively.
Notes:
To view Interrupts and Named Threads in Kernel Tracker, you must be running a WinCE Image that has Profiling Enabled (SYSGEN Variable IMGPROFILER=1). Not to worry, though. While profiling isn't enabled in our stock builds, you can usually still tell pretty quickly what each thread is doing based on its behavior.