Finding A Range of Events with Remote Kernel Tracker
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
When you view an event log in Kernel Tracker, you might find that a portion of the displayed log appears different, and that you are interested in exploring why. For example, you may see a period when there is an unusually large or unusually small amount of activity, or notice that a particular thread runs unexpectedly.
Once you identify a period of unusual activity visually in Kernel Tracker, you can use the Readlog viewing tool to examine the activity more closely.
The following steps can help identify a range of events in Kernel Tracker, and pass that information to Readlog for development that is more detailed.
To use Kernel Tracker to identify a range of events
In the Kernel Tracker display, note the period of activity you are interested in.
Select an approximate beginning point by clicking on the approximate time at which the range of interest starts. A vertical red cursor line appears that marks the time you clicked on, and Kernel Tracker displays the time stamp of the cursor line in the lower left corner of the Kernel Tracker window.
Note this beginning time stamp, including the milliseconds and microseconds.
Select an approximate end point by clicking on the approximate time at which the range of interest stops. A vertical red cursor line appears that marks the time you clicked on, and Kernel Tracker displays the time stamp of the cursor line in the lower left corner of the Kernel Tracker window.
Note this ending time stamp, including the milliseconds and microseconds.
To generate IDs for the events in a log, at a command prompt, type
Readlog –ids <MyLog>.clg <MyLog_IDS>.txtThis outputs a text file with an ID assigned to each event.
Open the text file created in Step 6. Using the time stamps noted in Step 3 and Step 5, identify the event IDs of the events with these time stamps.
To generate an output text file with only the events from the range of interest, use the
–rangeparameter alone. At a command prompt, typeReadlog -range <beginID> <endID> celog.clg MyOutput.txtThis creates an output text file that records the events that occured between beginID and endID.
You can also use Readlog to create alternative outputs that focus on a range of events.
- To generate an output file with the events from the range of interest together with a summary of those events, see Creating A Summary Of A Portion Of The Log.
- To create a new binary log file with only the events from the range of interest, see Creating a New Binary Log File with Events in a Range.