Fixed problems Release Notes

© Copyright International Business Machines Corporation 2008. 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 # IC56807
   2.2 APAR # PK64762
   2.3 APAR # PK65296
   2.4 APAR # PK68673
   2.5 APAR # PK69822
   2.6 APAR # PK70234
   2.7 APAR # PK70499
   2.8 APAR # PK70883
3.0 Component Test for C
   3.1 APAR # PK60317
   3.2 APAR # PK60914
   3.3 APAR # PK60937
   3.4 APAR # PK61027
   3.5 APAR # PK61031
   3.6 APAR # PK61429
   3.7 APAR # PK61520
   3.8 APAR # PK63341
   3.9 APAR # PK65458
   3.10 APAR # PK69530
4.0 Component Test for C++
   4.1 APAR # PK64594
   4.2 APAR # PK65426
   4.3 APAR # PK65738
   4.4 APAR # PK67311
   4.5 APAR # PK70083
   4.6 APAR # PK70916
   4.7 APAR # PK72816
5.0 Component Test for Java
6.0 Documentation - TestRT
7.0 Eclipse Integration
   7.1 RATLC01245188
8.0 GUI - TestRT
   8.1 RATLC01246749
   8.2 APAR # PK54078
   8.3 APAR # PK57986
   8.4 APAR # PK59106
   8.5 APAR # PK60228
   8.6 APAR # PK62442
   8.7 APAR # PK69523
9.0 Installation - TestRT
   9.1 APAR # PK60907
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 RATLC01246646
   17.2 RATLC01247201
   17.3 RATLC01247734
   17.4 APAR # PK55795
   17.5 APAR # PK60851
   17.6 APAR # PK66619
   17.7 APAR # PK70005
   17.8 APAR # PK70477
   17.9 APAR # PK71955
   17.10 APAR # IC58224
18.0 System Testing for C
   18.1 APAR # PK63044
   18.2 RATLC01244934
19.0 Target Deployment Port
   19.1 RATLC01246926
   19.2 APAR # PK36088
   19.3 APAR # PK60838
   19.4 APAR # PK61389
   19.5 APAR # PK66910

1.0 Code Review for C

None

2.0 Component Test for Ada

2.1 APAR # IC56807

The values in Target Deployment Port -> Library Settings -> Constant Definition tab (atc_nb_bit_branch and act_tio_file_name) do not appear in the project.

2.2 APAR # PK64762

With Component Testing for Ada, when using a "renames" statement on a package of itself like "package BASIC_TYPES.TYPES renames BASIC_TYPES;" then the definitions under this package are not visible.

2.3 APAR # PK65296

When using Component Testing for Ada, if pseudo-variable "I1" is used for part of elements in an array, then an error will occur at build time.

2.4 APAR # PK68673

Component Testing for Ada fails to resolve when an Ada95 keyword is used in an Ada83 test script.

2.5 APAR # PK69822

Component Testing for Ada test script compiler (attolpreproADA) never terminates in a specific case.

2.6 APAR # PK70234

When compiling a test script that stubs a function returning a value that is of a type specified in a user specification file, the Component Testing for Ada test script compiler (attolpreproAda) does not generate the "with" of this specification file in the "*_var_simule.ada" file. The Ada compiler then raises an error about the package not being found.

2.7 APAR # PK70499

When stubbing a function that should return a value, the code generated by the Component Testing for Ada test script compiler (attolpreproAda) contains a path that does not contain a return statement, which results in a warning message.

2.8 APAR # PK70883

When using Component Testing for Ada, and in the Ada program, there is a subtype declaration and the subtype of variable is used in the generated test script. If adding a tolerance delta to the expected value "EV", then compile error happens to the test driver.

3.0 Component Test for C

3.1 APAR # PK60317

Test Script generator for Component Testing for C generates duplicate definition of global variables when testing Static/Private data (##including the *.c file).

3.2 APAR # PK60914

The statement "STUB my_array 1...3 => ( {1,2,3} )" with 3 dots should fail with a syntax error message.

3.3 APAR # PK60937

When creating a new test script using the Component Testing for C Component Test Wizard, SERVICE blocks are created for functions that were not selected while working through the steps of the wizard. If there are functions in the file whose names are a subset of the name of the selected function, SERVICE blocks are generated for these functions in the test script file.

3.4 APAR # PK61027

Test reports for a Component Testing for C test do not display the expected value for members of a structure that are pointers.

3.5 APAR # PK61031

In a Component Testing for C test script, when stubbing a function that has a "signed char" array as a parameter, the array syntax cannot be used in the STUB statement. The C test script compiler will report a syntax error.

3.6 APAR # PK61429

The test script generator might generate a DEFINE STUB block name that contains an hyphen if the name of the stubbed file contains one, which would cause a syntax error when parsing the test script.

3.7 APAR # PK61520

Multiple C style comments in a single line distorts MC/DC coverage result.

3.8 APAR # PK63341

The runtime tracing viewer is launched despite the fact that the TRACE option is deselected in the TDP editor.

3.9 APAR # PK65458

When creating a new project and a new component test, the test creation wizard does not show the list of the detected functions (Unit Selection), it shows only one line under (File Selection). The metrics for the file are shown correctly.

3.10 APAR # PK69530

The HTML report generated is not correct when the test report contains serveral projects which contain nodes with the same name.

4.0 Component Test for C++

4.1 APAR # PK64594

When using the STUB statement with component testing for C++, if the STUB name contains the word "require" then it encounters an incomplete type error at build time.

4.2 APAR # PK65426

When using the STUB statement in Component Testing for C++, and if a STUB contains the 'extern "C"' statement, a link error occurs at build time.

4.3 APAR # PK65738

The Component Testing for C++ test generator generates garbage characters instead of a class name when a Trolltech QT class QString is used as a by-val parameter for a method.

4.4 APAR # PK67311

The following options are now accepted by any executable that relies on atl.opp:

--automatic_template_instantiation
--no_automatic_template_instantiation
--ii_file_name
--suppress_instantiation_flags
--template_info_file
--definition_list_file_name
--exported_template_file_name
--template_directory

4.5 APAR # PK70083

Component Testing for C++ test report generator fails with error when the intermediate trace file (.otd) is too large.

4.6 APAR # PK70916

Component Testing for C++ test script generator (atostart) abnormally terminates when analyzing the corba.h header file from the library Ace version 5.5.1 TAO version 1.5.1_1.

4.7 APAR # PK72816

The following C++ program gets an internal error from the C++ instrumentor (attolccp) when the option "-cond=modified", "-cond=compound", or "-cond=forceevaluation" is specified. An internal error is not produced when the option "-cond" (basic conditions) is specified.

struct s { int n; };
inline long f(struct s *p) { return !p || (p->n ? 0 : 1); }

5.0 Component Test for Java

None

6.0 Documentation - TestRT

None

7.0 Eclipse Integration

7.1 RATLC01245188

When performing runtime analysis and if the report is already open, adding Code Review in the settings, and rerunning, then the Code Review report is not opened automatically, even when double clicking on the results.xtp.
Workaround: Close the report and open it again by double-clicking on the results file.

8.0 GUI - TestRT

8.1 RATLC01246749

Files referenced in the project browser should not be cleaned by the clean action.

8.2 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.3 APAR # PK57986

The selection of scenarios in the Virtual Tester Driver List (Tab Scenario) does only work with the mouse.

8.4 APAR # PK59106

In the user interface (studio), changing a setting might cause the entire setting to disappear in some cases. For example, in the section "Linker" > "Additional objects or libraries" click on the ... to open up the edit window. In this window, you will see that the list of objects is duplicated. Delete part of the setting and click on OK. The settings window will be empty.

8.5 APAR # PK60228

On SuSE Linux Enterprise Desktop (SLED) or SuSE Enterprise Linux Enterprise Server (SLES) 10 and 10SP1, Studio will abnormally terminate if Syriac fonts are used.

8.6 APAR # PK62442

Exporting the metrics report using the menu entry File > Export might result in an abnormal termination.
Workaround: Use the menu entry Metrics > Generate HTML.

8.7 APAR # PK69523

When using the MC/DC level with code coverage, the tooltip showing the modified/multiple conditions is truncated when the expression is too complex.

9.0 Installation - TestRT

9.1 APAR # PK60907

TestRT fails to get the license when file descriptor has been set upper than 1024 on Solaris.

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 RATLC01246646

Java instrumentor aborts when building an already built test node on windows 2003 server.

17.2 RATLC01247201

The C++ instrumentor forgets to report an implicit default as a basic condition.

17.3 RATLC01247734

Generated filenames have changed on Windows. This impacts the following files:
- all instrumentors, every language, for Coverage, Trace, Mempro and Perfpro, .fdc and .tsf files
- ".aug" files (generated by attolcc1/attolccp when -keep option is set)
- .lsc files (attolcov source listings)

17.4 APAR # PK55795

On a source code line containing double comments, Code Coverage shows a magnifying glass where there is no need.

17.5 APAR # PK60851

Code Coverage shows a statement as executed after the "long_jmp" function, or after the function that calls the "long_jmp" function.

17.6 APAR # PK66619

C++ instrumentor fails with internal error when instrumenting stl_iterator.h (assertion failed).

17.7 APAR # PK70005

Using Code Coverage for Ada, and when using a loop statement, the following issues might occur:

1. When the program hits one of the exits, then all exits are shown as green
2. If the program hits one of the decisions in one of the cases, and the decision is negative, but the results show the exit for that case in green.

17.8 APAR # PK70477

Code Coverage command line report generator when used with option "-clean" does not work properly on some files.

17.9 APAR # PK71955

Instrumented C++ code fails to compile with gcc version 3.2.3.

17.10 APAR # IC58224

The "-ignore" option of the instrumentation launcher (attolcc) gives errors.

18.0 System Testing for C

18.1 APAR # PK63044

When the system testing runtime tracing viewer is opened the time is always displayed in milliseconds not in the format specified in the preference dialog box.

18.2 RATLC01244934

System Testing script compiler generates ATL_TIMEOUT corresponding to the first WTIME in the KO part and, if not present, to the first WTIME in the OK part.

19.0 Target Deployment Port

19.1 RATLC01246926

The attol_serv_95_smart.adb file should not contain the statement "with text_io;" as "text_io" is not available in SMART implementations.

19.2 APAR # PK36088

The TDP 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 TDP "epsilon" would be accepted as correct. The smaller range of the "delta" is not applied.
Workaround: Modify the "epsilon" value of the TDP runtime.

19.3 APAR # PK60838

When performing a clean build of a Component Testing for C test script, a warning is sometimes reported by the compiler when compiling the image.c file.

19.4 APAR # PK61389

When having a customized TDP that deals with the @ symbol, then the @ symbol can no longer be used for "const" parameters of a DEFINE STUB statement.

19.5 APAR # PK66910

Using Component Testing for C, dumping float numbers during test execution may overrun the buffer "atl_buffer".