Known problems Release Notes

© Copyright International Business Machines Corporation 2007. All rights reserved. US Government Users Restricted Rights - Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corp.

Release notes

1.0 Code Review for C
2.0 Component Test for Ada
   2.1 APAR#: PK47452
3.0 Component Test for C
   3.1 RATLC01193608
   3.2 APAR#: PK29374
   3.3 APAR#: PK48540
   3.4 APAR#: PK52074
   3.5 APAR#: PK55217
4.0 Component Test for C++
5.0 Component Test for Java
6.0 Documentation - TestRT
7.0 Eclipse Integration
   7.1 RATLC01244815
   7.2 RATLC01244839
   7.3 RATLC01244925
   7.4 RATLC01244805
8.0 GUI - TestRT
   8.1 RATLC01192961
   8.2 APAR#: PK51201
   8.3 APAR#: PK54078
   8.4 APAR#: PK54707
9.0 Installation - TestRT
   9.1 Open files limit on Solaris
   9.2 Cygwin cpcgnu installation on Windows Vista
   9.3 Installing Test RealTime with Microsoft Visual Studio
10.0 Integration with TestManager
11.0 Plug-in APEX
12.0 Plug-in Matlab
13.0 Plug-in RoseRT
14.0 Plug-in Visual
15.0 Plug-in TI Code Composer
16.0 Qualification Kit
17.0 Runtime Analysis
   17.1 APAR#: PK37016
18.0 System Testing for C
   18.1 APAR#: PK55196
   18.2 APAR#: PK55311
   18.3 RATLC01244934
19.0 Target Deployment Port
   19.1 RATLC01244570
   19.2 APAR#: PK36088

1.0 Code Review for C

None

2.0 Component Test for Ada

2.1 APAR#: PK47452

Some values of a 32 bit unsigned integer on a target that can only handle 32 bit integers cannot be tested using Component Testing for Ada. Exceptions are raised during the execution of the tests.

3.0 Component Test for C

3.1 RATLC01193608

In a Component Testing for C or Ada script, if comments are used in test with loop then these comments are duplicated many times in the report, which might cause the user interface to fail to display the report.

3.2 APAR#: PK29374

Component Testing for C generates test scripts that do not compile, when the source code under test includes global variables that are not seen from other modules.

 Workaround:

 At step 3/5 of the component testing wizard, one should select the option : "Component Under Test / <Test Name Value >" => Test Static/Private data or function = yes

3.3 APAR#: PK48540

Component Testing for C test script generator does not accept multibyte characters with '0x5c ('\') at the end of a line.

3.4 APAR#: PK52074

In a very specific case that involves macro definition and array declarations, the Component Testing for C script generator might forget to generate a STUB block for a function.

3.5 APAR#: PK55217

Component Testing for C test script compiler abnormaly terminates when a macro instantiation is longer than 2900 characters.

4.0 Component Test for C++

None

5.0 Component Test for Java

None

6.0 Documentation - TestRT

None

7.0 Eclipse Integration

7.1 RATLC01244815

When using the Component Testing for C or C++ feature within Eclipse on Solaris, then the test generation and execution fail with the error message about TestRTTestEnvFilePath.

7.2 RATLC01244839

When using Test RealTime within Eclipse, and when trying to create a new component test for C, then selecting "create only C test component" in the wizard, then going to the next page, and then back again, and selecting  "create empty test component", in that case, the Finish and Next buttons are grayed out.
Therefore, generating the test is not possible.
Workaround: Close the wizard and start over the test creation.

7.3 RATLC01244925

In the test suite editor in Eclipse for Component Testing for C on Linux, the initial height of the Test elements view is too small.
Workaround: click two times on the test element arrow to change the height back to normal.

7.4 RATLC01244805

When Rational Test RealTime 7.0.5 Eclipse plugin is installed on Rational Systems Developer 7.0.5 on Solaris 10 then when opening the Test execution test log, then the Eclipse UI freezes.

8.0 GUI - TestRT

8.1 RATLC01192961

The user interface does not detect Target Deployment Ports contained in a directory whose name includes a Japanese character.

8.2 APAR#: PK51201

On SUSE Linux SLES9-32 , and  with Gnome 2.4.1, using  the command  :  studioreport *.tsf  purifylt.tpf , the user interface terminates abnormally.
Workaround: Use another window manager version or OS version, or open the report from the user interface menu File > Browse Report.

8.3 APAR#: PK54078

On a Japanese PC using Windows, if no valid licenses are found or the license is going to expire, then a dialog will pop up and display a warning message that is corrupted. There is no clear indication of what user should do to resolve the license issue.

8.4 APAR#: PK54707

When using System Testing on a multi-processor computer such as a dual core, and during the execution of the test script, if a lot of information is printed out into the Build log then the user interface will abort without displaying any message or warning.

9.0 Installation - TestRT

9.1 Open files limit on Solaris

On Solaris, if the open files limit is lower than 1024, Test RealTime might not be able to access the licensing server, leading to a FLEXlm error -16,287.

To resolve this issue, set the open files limit to 1024 by typing the following command (in a bash environment):

ulimit -n 1024

9.2 Cygwin cpcgnu installation on Windows Vista

After installing Test RealTime on Windows Vista, the standard include files for the Cygwin cpcgnu/ana compiler are not correctly generated in the Target Deployment Port (TDP).


To fix this issue, after installing Test RealTime, open the /targets/xml/cpcgnu.xdp file in the TDP Editor and save it again to regenerate the TDP.

9.3 Installing Test RealTime with Microsoft Visual Studio

If you plan to use Test RealTime on Windows with Microsoft Visual Studio 6.0, .NET, or 2005 compilers, you must install Visual Studio and execute it at least once before installing Test RealTime in order to correctly initialize the Windows registry database. If you omitted to run Visual Studio before installing Test RealTime, the installation wizard produces an error message.

After installation, execute the following steps.

  1. Run and close Microsoft Visual Studio at least once
  2. Open a Windows Explorer and browse to the following directory: <install_dir>/targets/xml
  3. Double click the cvisual6.xdp (for Visual 6.0), cvisual7.xdp (for .NET), or cvisual8.xdp (for Visual 2005).. This opens the TDP in the Target Deployment Port Editor.
  4. Save the TDP to update the /targets/cvisual6, cvisual7, or cvisual8 TDP directory.

10.0 Integration with TestManager

None

11.0 Plug-in APEX

None

12.0 Plug-in Matlab

None

13.0 Plug-in RoseRT

None

14.0 Plug-in Visual

None

15.0 Plug-in TI Code Composer

None

16.0 Qualification Kit

None

17.0 Runtime Analysis

17.1 APAR#: PK37016

Inclusion of case statements by #include may cause the C++ source code instrumentor to display a warning message. Those statements might not be shown as covered in the Code Coverage Viewer.

18.0 System Testing for C

18.1 APAR#: PK55196

When running two virtual testers with System Testing, and when one of them at reach a RENDEZVOUS, the postprocessing phase is not launched by the user interface, and therefore no reports are generated.

18.2 APAR#: PK55311

Using the Virtual Test Driver Configuration window, the selection of instances is not saved when closing the user interface.

18.3 RATLC01244934

System Testing script compiler does not generate ATL_TIMEOUT value when WTIME is only in the OK part of the WAITTIL statement.

19.0 Target Deployment Port

19.1 RATLC01244570

On Windows Vista, the cpcgnu TDP is not correctly generated during the installation procedure.
Workaround: Open the TDP editor and regenerate manually the cpcgnu TDP.

19.2 APAR#: PK36088

The Target Deployment Port runtime for ADA defines a default "epsilon" value (for float types 1.0e-5, and for double types 1.0e-14). If the user defines a delta smaller than this, this would have no effect. Any result within the range of the Target Deployment Port "epsilon" would be accepted as correct. The smaller range of the "delta" is not applied.
Workaround:  Modify the "epsilon" value of the Target Deployment Port runtime.