How to Analyze CeLog Data (Windows CE 5.0)
To really take advantage of the information collected by CeLog, examine the information using two viewing tools, Remote Kernel Tracker and Readlog. Each tool provides unique insights. You can use the graphical representations from Remote Kernel Tracker to maximize the usefulness of the detail presented by Readlog.
To track your progress in the following table, select the check box that corresponds to each step.
Step | Topic | |
---|---|---|
1. Collect CeLog event tracking data by executing CeLogFlush.exe.
The data will be stored in a log file whose location is determined by the registry and command-line settings you use with CeLogFlush.exe. For more information, see CeLogFlush Registry Settings and CeLogFlush Command-Line Overrides. |
Collecting Data on a Standalone Device with CeLogFlush | |
2. If necessary, copy the log file to the flat release directory.
If the file is in the flat release directory, you must prevent CeLogFlush from writing to the log file at the same time you view it. To prevent unwanted access to the log file by CeLogFlush:
|
Not applicable | |
3. To make identifying thread activity as easy as possible, create a new log file that replaces thread handle values with fixed thread names. | Fixing Thread Names With Readlog | |
4. View the log file you created in step 3 in Remote Kernel Tracker. | Starting Remote Kernel Tracker in File Mode | |
5. When the file opens in the graphical view, examine the thread activity.
For example, zoom out to the largest setting (10000), and then zoom in on periods of activity you wish to examine further. |
Data Selection and Analysis | |
6. To analyze a smaller portion of the log in more detail, find the event range that defines that portion of time. | Working with Event Ranges in Readlog | |
7. To get more detail about activity, create a summary of the events from the entire log file or from the event range of interest. | Creating a Summary of a Portion of the Log |
See Also
Remote Kernel Tracker | Readlog Viewing Tool
Send Feedback on this topic to the authors