© 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
The Ada test script compiler generates lines that are too long for the Ada compiler when testing arrays.
Procedure call in stubs are not followed by ';' when the call is in a control statement (if , loop ...).
Component Testing for Ada script compiler generates procedures for all the Ada types found in the application under test whether or not they are used. If a large number of types are not used, this would cause a lot of unnecessary code to be generated, compiled and embedded on the target.
Internal error raised by the Component Testing for Ada test script generator why generating stubs for generic separate packages.
The Component Testing for Ada test script generator creates an empty SERVICE block in specific case.
The Component Testing for Ada test script compiler raises an internal error when compiling a test which contains a constrained array and when the option NOALLOC is used.
In the user interface, empty tests are not displayed in the Component Testing for C reports.
In System Testing, the loop identifier I8 might conflict with a user defined variable or type.
Define the macro RTRT_IDXVAR_7_MAX to remove the declarations I8 to I20 and J8 to J20.
When Component Testing for C is parsing a test script containing nested INCLUDE PTU instructions and within each included test script there are IF / ELSE / END IF instructions then the following errors occur:
TestRT-E-TROPSINON, [script.ptu:11] The keyword ELSE doesn't match with a keyword IF.
In a Component Testing for C script, trying to initialize a multidimensional array where all dimensions are of size 1 will causes the following warning message when generating the report: Mismatch between files .RIO and .TDC incoherent dimension in the current array.
The report will still be generated correctly.
Backslash at the end of an include path causes incorrect perl code in environment node to be generated.
Component Testing for C test script complier generates hardcoded pointer definition (void *), which cannot be customized to a specific target environment. This might results in the following error message on some target environments: "invalid narrow pointer cast".
Support for MS VC 2005 specific extension: integer-suffix "i64".
In a Component Testing for C script, using the NB_RANDOM statement causes floating point variables to be used even for integer types.
Instrumenting an application that uses the keyword, _Bool, which is a ANSI C99 Standard, causes a syntax error.
When stubbing a function that takes a parameter that is of type union, the Component Testing for C test script compiler generates incorrect code to initialize the union field selector.
When exporting the Component Testing reports to HTML, the HTML filenames which should have the same filename as function under test are truncated to 13 characters.
Wrong line number might be given in instrumentation error message when using Component Testing for C++.
Component Testing for C++ parser does not interpret correctly the vendor specific push_macro and pop_macro pragmas.
Component Testing for C++ generates an error on a C++ style casting.
Component Testing for C++ script compiler generates C++ code that fails to compile with error "qualified name is not allowed" in some specific cases.
None
The chapter "VAR, ARRAY and STR <expected> Parameter" [C language] of the User Guide lists, among other parameters, DELTA.
However, the statement STR does only accept the following options: init=, init ==, ev =, ev ==.
None
In the Basic Settings for a TDP adding a Key called "ATTMODE" and setting it to a value of 0 will cause to new projects created using this TDP to have the "Build options" "Runtime tracing" check box to be un ticked and grayed out. However when instrumenting the -trace option is still passed to the instrumentor leading to linking errors.
When one use the "Generate HTML" feature of the user interface, the memory used is not freed.
Using this feature again will consume extra memory.
Tests are wrongly reported as failed when the report is split.
The Target Deployment Port generated files do not contain the "Pragma preelaborated" statement if the coverage option is set to "-INIT_UNSUPPORTED".
When the virtual tester is deployed on a remote Linux computer the automatically generated supervisor file contains a COPY instruction to copy the test result file, .RIO, from the remote computer to the local computer. The COPY instruction uses the /ASCII option which causes a Ctrl+M character to be introduced into the copied file on the local computer.
None
None
None
None
The TestRT plugin into RoseRT fails to recognize the capsule name in source code if some comments have been added before the line where the capsule is defined. The test report will show "Unknown capsule" numbered from 1 to N.
Instrumentation of any VC++.NET 2005 application from VS.NET 2005 IDE generates the fatal link error – LNK 1181: cannot open input file ‘./TP.obj’.
None
None
On AIX, when the instrumentation of a source file fails, or when a file is excluded from instrumentation (using the -ignore option, for example), the following error message is displayed: "xlC: 1501-228 input file not found".
In some cases, C++ instrumentor fails to instrument templated function in a non-template class.
Support for MS VC 2005 specific extension: integer-suffix "i64".
Instrumented code that includes the <list> header file cannot be compiled by GNU compiler, g++.
C code instrumentor fails with syntax error due to unnamed structs/unions.
False positive memory leaks (MLKs) are reported when a large numbers of potential memory leaks (MPKs) are detected.
When instrumenting pre-elaborated files with Code Coverage for Ada, under certain circumstances an circular dependency in the closure of the code.
Not all Test RealTime error messages are prefixed with a specific label that would help to identify them.
Code Coverage for Ada generates code which does not compile in a specific case.
Code Coverage for Ada generates code which fails to compile in a specific case with error message "preelaborate unit cannot depend on non-preelaborated unit".
When analysing a very long VAR line, the System Testing for C test script compiler terminates with the error message "TestRT-F-LEXTKTLNG Lexical identifier too long".
When adding a long string to the output buffer via the function atl_buffer_add() it is possible to overrun the end of the buffer in the case where atl_buffer_next is equal or superior to atl_buffer_slack. At worst this leads to an abnormal termination of the test harness, at best strange characters in the output file and an error during the report generation.
When cygwin compiler and the Test RealTime project files are located on different drives, the generated atl.opp is not correct and the system include files are not excluded from the instrumentation.
The Target Deployment Port generated files do not contain the "Pragma preelaborated" statement if the coverage option is set to "-INIT_UNSUPPORTED".
The Target Deployment Port initialisation function is not protected against multiple initialisations by multiple threads.