Reading SpyKer Event Trace Data Debug, diagnose and optimize embedded system performance

Attach to running deployed targets.
Since SpyKer does not require an instrumented kernel, any development or deployed system can be traced.

1. What is SpyKer?
2. What does a trace tool do?
3. No kernel rebooting or instrumentation required
4. >>Reading SpyKer event trace data
5. Remote targeting of event traces
6. Selective event tracing and buffering for crash analysis
7. SpyKer Pro PDF brochure (203 kB)

Go ahead and interact with your application's trace data. Difficult-to-understand relationships within the application immediately become clearer with SpyKer's powerful front-end visualization capabilities.

Event data in your embedded system is displayed in an easy-to-comprehend fashion, with multiple windows and visualizations simultaneously available on-screen.

• Invoke pop-up boxes to display information about cursor-selected events
• Zoom in or out around areas of interest in event data
• Filter events and "jump" specific system calls or other events
• Accurately measure times between different events

Events are displayed as aspects of the processes that are running. SpyKer can trace system calls, interrupts, context switches, processor exceptions and many other events. Developers can also use SpyKer to insert trace entry points into their application or device driver code and collect event data.