background image
<< Performance Profiling Viewer Preferences | To jump to the corresponding portion of source code >>
<< Performance Profiling Viewer Preferences | To jump to the corresponding portion of source code >>

How Runtime Tracing Works

Runtime Analysis
Runtime Tracing
Runtime Tracing is a feature for monitoring real-time dynamic interaction analysis of
your C, C++ and Java source code. Runtime Tracing uses exclusive Source Code
Insertion (SCI) instrumentation technology to generate trace data, which is turned
into UML sequence diagrams within the Test RealTime GUI.
In Test RealTime, Runtime Tracing can run either as a standalone product, or in
conjunction with a Component Testing or System Testing test node.
You associate Performance Profiling with an existing test or application code.
You build and execute your code in Test RealTime .
The application under test, instrumented with the Runtime Tracing feature,
then directs output to the UML/SD Viewer, which a provides a real-time UML
Sequence Diagram of your application's behavior.
How Runtime Tracing Works
When an application node is executed, the source code is instrumented by the C, C++
or Java Instrumentor (attolcc1, attolccp or javi). The resulting source code is then
executed and the Runtime Tracing feature outputs a static .tsf file for each
instrumented source file as well as a dynamic .tdf file.
These files can be viewed and controlled from the Test RealTime GUI. Both the .tsf
and .tdf files need to be opened simultaneously to view the report.
Of course, these steps are mostly transparent to the user when the test or application
node is executed in the Test RealTime GUI.
Understanding Runtime Tracing UML Sequence Diagrams
The lifeline of an object is represented in the UML/SD Viewer as shown below.
The instance creation box displays the name of the instance. For more information
about UML sequence diagrams, see UML Sequence Diagrams.
Below is an example of object lifelines generated by Runtime Tracing from a C++