© 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.
None
Component Testing for Ada report generator abnormally terminates.
Entity "..." was not found when instantiating a type operator of a generic parameter (use type).
Component Testing for Ada forgot to copy the representation clause into the generated code for a STUB statement.
The test script compiler generated incorrect code when testing certain structures that had been initialized separately but tested against an existing structure.
Unable to stub a generic package procedure on a separate package with a _NO modifier.
If a line in the DDT file generated by the test script compiler for Ada is longer than 132 characters then the line may be truncated in the wrong place leading to an error in the report generator.
Ada test script compiler produces syntaxic errors due to internal buffer overflow when analysing a large amount of ada code in the test script.
If an array element was used in a variable evaluation, Component Testing for Ada terminated with the error message "CASE overflow in the module generate_tabular_recursive_code".
The number NaN as defined by IEEE 754 should be better processed by Component Testing for C when doing comparison.
A test script that has a name with an accented character in it causes the report generation to fail.
A test was set up for the math function sin(x) and two of the input/expected values test the special values Inf and NaN. While the test report displays the same Expected and Obtained Values, the test appears to fail.
Test Report Generator terminates with an internal error message.
The Component Testing for C and Ada Wizard, there is a selection for "Node Creation Mode" for choosing either "Multiple Mode or "Single Mode" for step 3/5 "Test Script Generation Settings". This selection (Node Creation Mode) is missing from Test RealTime version 7.0.
In a Component Testing for C script, when the init value was not defined, the report contained unexpected characters, for example: "STRUCT myStructC, ev== "
Component Testing for C script generator - attolstartC - terminates abnormally when analyzing a specific line with a syntax error.
Component Test for C does not compute correctly numbers at the limit, since it does not propagate the sign bit.
rod2xrd fails when trying to generate the report in another location.
Instrumentor aborts when instrumenting test case for classes derived from Boost libraries.
Linking the TDP as a DLL fails when the multi-thread option is enabled.
Component Testing for C++ fails with cannot access private class declared in class 'LList'.
The following fatal internal error is raised by Component Testing for C++ script generator (atostart) when attempting to process a template method: "atostart - fatal: internal error: appel de XYZ sur un type 'template parameter'"
In the user interface, the Asset Browser does not display testcases of a Component Testing for C++ script when included in a nested test classes.
In a Component Testing for C++ script file, if a COMMENT line is empty, the corresponding line in the report will contain unexpected characters .
Component Testing for C++ test script generator abnormally terminates with message "atostart - fatal: internal error: lors de RecenseVariable, fichier conteneur NULL".
Component Testing for C++ test script generator - atostart - abnormaly terminates when analyzing Boost library.
Component Testing for C++ test script generator produces source code that compiles with errors.
Component Test for C++ display an invalid gnu version error message while reading the file atl.opp.
Component Testing C++ script generator aborts on files using Boost libraries.
A debug message is displayed when the locale is 'ja_JP'.
None
None
Each time the user clicks on a report link, a new source editor is opened instead of reusing the already opened one. This is fixed with Eclipse 3.2. The code review report still opens another editor containing the same source file with Eclipse 3.1.
After exporting to HTML a report for a project with children projects, the hyperlink in the main page is pointing to the same report for all the different child projects.
The name of some performance and memory reports were not descriptive enough.
Trying to export very large Component Testing for C or Ada report (.xrd file of more than 50MBytes) to HTML format makes the user interface terminates abnormally.
In the Target Deployment Port Editor, when keys use the notation $ENV{'MY'} where the env MY is set above using the notation ENV_SET_IF_NOT_SET the keys are not set properly.
None
None
None
None
RoseRt plug-in doesn't take into account $@ used in UserObjectFiles.
None
None
None
Syntax error when analyzing ANSI C99 declarations in the middle of statements.
Instrumentation option -dumpcalling with -trace produces code that does not compile.
The C instrumentor does not handle #pragma statements over several lines.
Ada source code parser failed to find unit.
When the source code being instrumented is using function typedefs such as "typedef int (BINARY) (int,int);", the instrumentor for language C generates incorrect code that raises the error "illegal sizeof operand".
C++ Source code instrumentor abnormaly terminates when parsing a very long template note.
The instumentor for the C language does not accept __asm instruction without braces.
C99 style contant arrays are not supported by the C source code instrumentor.
The Test RealTime Instrumentor for C, when using "--block=logical" inserted branch tracking code into expressions inside array declarations (both in typedefs and real declarations). Some programmers rely on constant folding and the ternary operator to implement compile-time dynamic array sizing. When the instrumenter then inserts tracking code the size will no longer be a constant expression and the compilation will fail.
linkedDLL.bat in example SharedLibrary builds with error.
System Testing for C generates a report even if the Report Generation option is disabled in the user interface.
After several succesive runs with on-the-fly runtime tracing, it is no more possible to launch the test. The following error message: " Error: No TDF channel available for dynamic sequence diagram" is displayed in the "Messages" tab of Studio's output window.
Virtual Tester Driver Configuration is not updated when a pts file included in the main .pts file in modified.
System Testing report generator fails when virtual tester has aborted on rendez-vous timeout.
The Target Deployment Port ignores any additional ssh/rsh options in the basic setting : REMOTE_CONNECTION.
The Target Deployment Ports cwince5.xdp and cwince.xdp contain duplicate free in the tracking user-defined memory functions.
Smart restriction is not completely supported, the expression 'image is used in the TDP file attol_comm.adb.
The Target Deployment Port wince5SP5.xdp missing support for keywords __unaligned and __forceinline.