Fixed problems Release Notes

© Copyright International Business Machines Corporation 2009. 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
   1.1 APAR # PM01768
2.0 Component Test for Ada
   2.1 APAR # PK91512
   2.2 APAR # PK98253
   2.3 APAR # PK98632
   2.4 Defect # RATLC01493457
3.0 Component Test for C
   3.1 APAR # PK79720
   3.2 APAR # PK85935
   3.3 APAR # PK97613
   3.4 APAR # PK98650
   3.5 APAR # PM00208
   3.6 APAR # PM00507
   3.7 APAR # PM02641
4.0 Component Test for C++
   4.1 APAR # PK82857
5.0 Component Test for Java
6.0 Documentation - TestRT
7.0 Eclipse Integration
   7.1 Defect # RATLC01244839
8.0 GUI - TestRT
   8.1 APAR # PK70674
   8.2 APAR # PK76398
   8.3 APAR # PK82326
   8.4 APAR # PK83010
   8.5 APAR # PK87244
   8.6 APAR # PK93273
   8.7 Defect # RATLC01371451
9.0 Installation - TestRT
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 # PK73251
   17.2 APAR # PK96448
   17.3 APAR # PK98987
   17.4 APAR # PK98988
   17.5 Defect # RATLC01359902
18.0 System Testing for C
   18.1 APAR # PK73553
19.0 Target Deployment Port
   19.1 APAR # PK98289

1.0 Code Review for C

1.1 APAR # PM01768

Code Review generates a false positive for rule M1.1 in some cases with error message "floating constant is out of range".

2.0 Component Test for Ada

2.1 APAR # PK91512

Component Testing for Ada test script compiler (attolpreproADA) generates incorrect Ada code with error: Inappropriate operands for "DOT_DOT" operation.

2.2 APAR # PK98253

A warning should be generated instead of a fatal error when the overloading of environment variables for VAR statement with dynamic array indexes is detected by Component Testing for C.

2.3 APAR # PK98632

Component Testing for Ada test script compiler might generate incorrect Ada code when the test script is dealing with arrays of structure.

2.4 Defect # RATLC01493457

The description of -EXUNIT and -EXCALL in the documentation has been updated.

3.0 Component Test for C

3.1 APAR # PK79720

User interface terminates abnormally when opening a very large Component Testing for C report.

3.2 APAR # PK85935

Component Testing for C test script compiler may wrongly detect a syntax error on a typedef declaration using a forward reference.

3.3 APAR # PK97613

Component Testing for C might terminates abnormally when parsing IF/END IF statement that contains back slash characters.

3.4 APAR # PK98650

Component Testing for C test script compiler should not display warnings due to the use of Code review pragmas "#pragma attol crc_justify".

3.5 APAR # PM00208

Code instrumentor (attolcpp) terminates with a fatal error when parsing a function with parameters starting with "@far @gpage" compilation directives.

3.6 APAR # PM00507

Component Testing for C test script generator (attolstartC) does not recognize the "stop_analyze"/"start_analyze" directives but only "stop_analyse"/"start_analyse" which is in contradiction with the online help.

3.7 APAR # PM02641

The target deployment port cwinmulti.xdp should not use the option "--gnu=none" in the parser settings, since this option is not recognized.

4.0 Component Test for C++

4.1 APAR # PK82857

Even with "Test class friend of tested classes" option enabled, a compilation error occurs when compiling a test class (.otd) that invokes the protected constructor or destructor of a tested class.

5.0 Component Test for Java

None

6.0 Documentation - TestRT

None

7.0 Eclipse Integration

7.1 Defect # 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.

8.0 GUI - TestRT

8.1 APAR # PK70674

Incomplete PostScript (*.ps) generation with large amount of data to be processed.

8.2 APAR # PK76398

The user interface (studio) will not interpret correctly a path which start with the drive letter in upper case when the actual path to the working directory is in lower case.

8.3 APAR # PK82326

The command line "studio -view project.rtp" does not open runtime trace reports.

8.4 APAR # PK83010

Studio does not parse the command line parameters correctly when there are spaces in the file names.

8.5 APAR # PK87244

On a RedHat Enterprise Linux 4.0 (base) environment, when the LANG environment variable is set to zh_CN.UTF-8 (Simplified Chinese) then Test RealTime will terminate with a SIGSEGV when clicking the OK/Cancel/Finish button in a number of locations in the GUI which include:
- File->Open...->Project...
- File->Open...->File...
- File->New->(Next until Finish is available)->Finish
where the Open issues will only occur if you first select a file with the mouse and then click OK/Cancel.

Working around this is possible via keyboard interaction with the File->Open dialog rather than mouse interaction.

8.6 APAR # PK93273

On Solaris systems when selecting a text with the mouse pointer in the Component Testing for C report, TestRT GUI studio terminates abnormally.

8.7 Defect # RATLC01371451

The IBM Rational Test RealTime user interface (studio) "About" dialog box should display the build number of all the Test RealTime command line tools installed on the user's computer.

9.0 Installation - TestRT

None

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 # PK73251

On Linux, Studio does not update the current file name or function name after you click on a function call hyperlink.

17.2 APAR # PK96448

Instrumentor for C (attolccp) terminates abnormally with the message INTERNAL ERROR: Bad assertion #4 while computing composition, when analyzing a specific expression with operator ^.

17.3 APAR # PK98987

The C/C++ instrumentor in TestRT 7.5.0.0 might generate incorrect code that fails to compile with error "label at end of compound statement" when instrumenting a switch/case statement that also involves goto and label statements.

17.4 APAR # PK98988

The C/C++ instrumentor sometimes generates incorrect code when the -c99 option is specified and goto statements are used.

17.5 Defect # RATLC01359902

It should be possible to only display memory leaks that are associated with a call stack. Memory allocations that occurred before the application started do not have a call stack and therefore, should not be included in the Memory Profiling report.

18.0 System Testing for C

18.1 APAR # PK73553

Using the Wizard to create a new System Testing test, on page 4/7 "Generating New test Script", the Settings button does not work, the Settings window is not display.

19.0 Target Deployment Port

19.1 APAR # PK98289

When using the ATQ Dump Driver API to dump the test results, the min max data for Performance profiling are not dumped out.