winIDEA Help

In this topic:

•Trace

•Profiler

•Profiler Statistics

•Coverage

 

 

Introduction

Analyzer is a powerful tool, which enables you to record the program execution trace, data trace or other trace messages and then analyze these recordings to produce coverage or timing measurements; with the BlueBox Debuggers and its Add-on modules (ADIO and CAN/LIN).

Analyzer window can show several aspects of the recording in different windows.

 

 

 

Trace

Trace provides deepest possible insight in the real-time workings of the application. The quality of captured information depends on trace capabilities of the CPU and the used trace tool, and can include:

•Program trace

•Data trace

•Instrumentation trace

•Auxiliary I/O trace

 

Trace view reconstructs the low level captured events to:

•Program counter movement

•Instruction flow on assembly level

•Source code flow

•Data variable read/write accesses

•Labels (association between the address and a symbol obtained from the download file)

 

 

Profiler

Profiler is a real-time analysis tool, which uses the acquired trace information to derive high-level analysis of the application real-time behavior. The profiled information is displayed in the Profiler Timeline Window and in the Profiler Statistics Window.

 

Based on the acquired trace information, the Profiler can determine:

•How many times an event occurred

•How long did the event last

•The minimum, maximum and average event duration

•The period between consecutive event occurrences

•Sequence of various events

•Time between arbitrary events

 

Any data that can be recorded with BlueBox tools can be used as a basis for the analysis of:

•Program execution (function execution)

•Data accesses (data writes and reads, OS events)

•Instrumentation messages (custom event signaling, OS events)

•Network messages (CAN, LIN messages)

•Digital/Analog IO signals

 

Recorded data is automatically processed by winIDEA. In addition, you can also do custom post processing analysis by configuring configuring Profiler Inspectors. Inspectors generate events derived from the recorded ones. You can use them to analyze event chains, measure time constraint violations and much more.

 

 

Profiler Statistics

Profiler Statistics offers different types of statistics information:

•Interval Statistics

•Area Statistics

•Session Statistics

 

Event types are:  

•Entry

•Resume

•Suspended

•Exit

•Write

 

Task (context) and functions states are:

•Active

•Inactive

•Suspended

 

Profiler Statistics in displayed in the Profiler Statistics Window.

 

 

Coverage

Code coverage is a measurement used in software testing, an indirect quantitative measure of test quality. It helps:

•Find areas of a program not exercised by a set of test cases, indicating some code could still contain critical errors.

•Find code that is never executed. So-called “dead code” represents undesired overhead when assigning memory resources and is a potential hazard since it was not tested.

•Identify redundant test cases (that do not increase coverage).

 

For more information, refer to Coverage.

 

 

Exporting the data

Refer to Exporting the data for more information.