Troubleshooting Rose RealTime Integration

In some cases, conflicts or problems may prevent the Rose RealTime integration to work as expected. The following tables sum up some of the issues that may occur, and explains how to solve them.

Project instrumentation and compilation

Problem

Solution

Instrumentation options cannot be changed

The component or model is read-only.
Change the component to read-write status.

An .fdc correspondence file is not found during instrumentation

The component Cov or Cov/Model directory may have been destroyed, for example by a Clean command.
To restore the lost information, run the Enable Instrumentation of Selected Component command.

New settings are ignored after performing an Enable Instrumentation of Selected Component command

Quick Build does not regenerate makefiles.
Run the Rebuild command instead of a Quick Build.

An error message states that an Instrumentor is missing during instrumentation

Another component for which no Instrumentation Launcher (attolcc) is available, or no link exists between the Rose RealTime code generation and the TDP, has been enabled with Enable Component Instrumentation.
Only enable components for which a complete configuration exists.

 

Project link

Problem

Solution

An application cannot be instrumented with instrumented libraries

Activate the Add TDP option for the application component. The plug-in automatically scans application dependencies and adds the TDP.Obj of instrumented libraries to the User Obj.

Note   Instrumentation options must be the same for all libraries.

An application cannot be instrumented with external instrumented libraries

The Rose RealTime plug-in does not know where TDP is generated when external components are used. In this case, create an external library that contains TP.obj.

 

Execution

Problem

Solution

Multithreading issues

Check that the Multithreading instrumentation setting is correctly configured.

Link issues

When multiple subcomponents are involved in a component (libraries and binary), check that instrumentation options are the same for all components and that the TDP.obj is correctly linked.

Instrumentation issues

Check that no warning message appears during instrumentation. It may be necessary to exclude one or several components from instrumentation (attolcc -exunit). See the Reference section for further information about Instrumentation Launcher command line options.

 

Results

Problem

Solution

Files are missing when the Test RealTime is launched to display report files. Code Coverage results are missing or display the entire application as uncovered.

The runtime analysis trace dump was interrupted. Dumps can take a long time, especially when the Memory Profiling feature is in use. See Generating SCI Dumps for more information.

Missing files on another component

The plug-in offers to display all the results for enabled components.  

Disable the any components that are not under analysis.

No coverage results on a diagram

Check that the component was correctly generated with the Code Coverage instrumentation option.

Check that the component is enabled for instrumentation. The Plug-in only changes state diagrams for enabled components.

Check that the component is not read-only, such as for an inherited diagram.

 

Related Topics

Generating SCI DumpsSource Code Insertion TechnologyWorking with Rational Rose RealTime