Event Tracking
Microsoft® Platform Builder offers an event-tracking subsystem (Celog.lib) in Nkprof.exe. Activating this feature during development can help you resolve bugs and improve platform performance by tracking and recording what is taking place in the system. For information about enabling and configuring the Event Tracking feature, see Event Tracking Implementation.
The event-tracking subsystem can be used in anywhere in Windows CE: the kernel, the core libraries, or in user and OEM application components. It can work on any build and can be started at any time.
By default, the event-tracking subsystem logs all events except KCALL entry and exit points in a file called Celog.clg. To narrow the data collected to the information you want, you can use collection zones to select certain data streams. For information about collection zones, see Enabling Events and Zones During Boot.
Windows CE global variables
The following table shows the global variables used for configuring Event Tracking.
| Global variable | Description |
|---|---|
| dwCeLogLargeBuf | Adjusts the size of the main tracking buffer. |
| dwCeLogSmallBuf | Adjusts the size of the secondary tracking buffer. |
Windows CE tracking functions
The following table shows functions used by the kernel for Event Tracking.
| Function | Description |
|---|---|
| CeLogData | Called by the kernel whenever an event occurs that can be tracked. |
| CeLogInterrupt | Called by the kernel when an interrupt occurs and before the interrupt service routine (ISR) is called, and again when the ISR returns to the kernel. |
| CeLogSetZones | Called to change the current tracking zones. |
| CeLogThreadMigrate | Called by the kernel when a thread migrates between processes. |
| CeLogReSync | Called to cause the tracking engine to dump all current threads and processes. |
See Also
Last updated on Friday, October 08, 2004
© 1992-2003 Microsoft Corporation. All rights reserved.