CeLog Event Tracking Overview
Other versions of this page are also available for the following:
.gif "A hyphen indicates that the information in this topic is not relevant for this platform, or that the platform does not support the API that is listed.")
.gif "A checkmark indicates that the information in this topic is relevant for this platform, and that any API listed is also supported on this platform.")
8/27/2008
CeLog is a general-purpose event-tracking tool that logs a set of predefined kernel and coredll events. CeLog also exposes a library of functions that can be used anywhere for logging user-defined events, or for controlling event tracking.
CeLog collects data and stores it in a user-configurable location, such as the release directory of the host computer or the root of the device file system. The data can be viewed on the host computer using a graphical viewer, Remote Kernel Tracker, or a non-graphical text reader such as Readlog. The graphical view provided by Remote Kernel Tracker can help you visualize the activity on your system and develop an overall idea of interactions between threads and processes. The text output provided by Readlog can help you learn details about small, focused pieces of the log that you are interested in.
The simplest way to collect CeLog data is to connect the Kernel Tracker tool to a device. The tool enables real-time CeLog data collection, transports the data to the host PC, and then displays it graphically.
You can also collect CeLog data by building a run-time image with event tracking enabled. In the default configuration, when a Windows Embedded CE–based device begins running a run-image that has event tracking enabled, the CeLog flushing application CeLogFlush.exe creates a file named Celog.clg in the %_FLATRELEASEDIR% directory. This is a file of raw data, which is updated periodically as your device runs.
The data that CeLog captures is divided into zones that are similar to debug zones. Zones allow you to filter the logging output, and collect only the data you are interested in. Zones can be set from the development workstation or from the device.
See Also
Tasks
Enabling CeLog Event Tracking in a Run-Time Image