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
2.0 Component Test for Ada
   2.1 APAR# PK91618
   2.2 APAR# PK92324
   2.3 APAR# PK92809
3.0 Component Test for C
   3.1 RATLC01374163
   3.2 APAR# PK92102
   3.3 APAR# PK93293
   3.4 APAR# PK93785
   3.5 APAR# PK95388
4.0 Component Test for C++
5.0 Component Test for Java
6.0 Documentation - TestRT
   6.1 APAR# PK71612
7.0 Eclipse Integration
8.0 GUI - TestRT
   8.1 APAR# PK95475
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# PK66620
   17.2 APAR# PK86576
   17.3 APAR# PK88488
   17.4 APAR# PK88499
   17.5 APAR# PK88504
   17.6 APAR# PK88584
   17.7 APAR# PK90111
   17.8 APAR# PK94144
   17.9 APAR# PK95196
   17.10 APAR# PK95370
18.0 System Testing for C
19.0 Target Deployment Port
   19.1 APAR# PK88122

1.0 Code Review for C

None

2.0 Component Test for Ada

2.1 APAR# PK91618

Component Testing for Ada does not detect invalid Boolean values at runtime resulting in an incorrect report showing a failed test with both the Expected value and the Obtained value as TRUE.

2.2 APAR# PK92324

The attolchop.exe command returns "0" as return code, when it should return "3" or "5"

2.3 APAR# PK92809

Component Testing for Ada test script compiler terminates abnormally without an error message, when the command line is too long.

3.0 Component Test for C

3.1 RATLC01374163

In the user interface (studio), it is not possible to use two different and independent test scripts for two different source code files in the same test node of a project, because the augmented file after compiling the first test scripts gets overwritten by the second test script.

3.2 APAR# PK92102

The memory profiling capabilities might incorrectly report a memory leak before the exit of the function when using _atl_obstools_dump(1) in some cases.

3.3 APAR# PK93293

Component Testing for C test script compiler generates incorrect source code in some cases where an anonymous union is used in a structure type.

3.4 APAR# PK93785

Component Testing for C test script generator (attolstartC) terminates abnormally against code having huge size of array.

3.5 APAR# PK95388

Component Testing for C test script compiler generates source code with a local variable named "res" which might cause a name conflict at compilation.

4.0 Component Test for C++

None

5.0 Component Test for Java

None

6.0 Documentation - TestRT

6.1 APAR# PK71612

In Component Testing for Ada, when using the expression "ev=init" in a VAR statement, the pseudo variable "init" should be evaluated after the execution of the code under test, and not before.

7.0 Eclipse Integration

None

8.0 GUI - TestRT

8.1 APAR# PK95475

Report files are not generated in the specified directory ($OUTDIR) if this directory does not exist.

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

When instantiating a template with a void parameter and a method takes a parameter of the template instantiation type the C++ instrumentor complains with an error message.

17.2 APAR# PK86576

The launcher "attolcc" does not handle correctly the option '-Wl,-(' -lpl_multi '-Wl,-)' .

17.3 APAR# PK88488

The C/C++ instrumentor (attolccp) generates incorrect code when instrumenting a return statement in a switch statement.

17.4 APAR# PK88499

C instrumentor (attolccp) generates incorrect code for coverage when instrumenting code using goto and label statements in a switch case.

17.5 APAR# PK88504

When instrumenting macros containing statement expressions the use of the macro is not indicated with a magnifying glass and the conditions in the macro are not instrumented.

17.6 APAR# PK88584

The C/C++ instrumentor generates incorrect code in some cases where the ternary operator (x?y:z) is used with an anonymous structure type.

17.7 APAR# PK90111

Ada instrumentor (attolada) fails with error " Entity not found" in some cases that involve first and last type resolution on a generic array type.

17.8 APAR# PK94144

The C/C++ instrumentor generates bad code in a specific case of a complex function using a variable length array, a switch statement with a return, and a final return statement.

17.9 APAR# PK95196

The memory profiling capability for C++ might generate incorrect code in a specific case, which will result in the following compiler error message: Cannot access protected typedef declared.

17.10 APAR# PK95370

When a program has a structure and its instance, and both have the same name, the instrumentor might generate an invalid C code.

18.0 System Testing for C

None

19.0 Target Deployment Port

19.1 APAR# PK88122

TDP clinuxgnu2_95 gets instrumentor error for "__FUNCTION__"