Release Notes - VectorCAST: 6.4.6 VectorCAST/C,C++, Ada (Core) 81243: Crash while closing windows Previously, VectorCAST experienced a crash when the user closed a window that resulted in a process that closed other windows that were already pending to be closed. This problem has been fixed in VectorCAST version 6.4.6 and VectorCAST version 2018 SP3. VectorCAST/Ada: 73561: DEOS Ada compiler not always linking instrumented harness correctly Previously, when an Ada environment built with the DDCI/Score compiler was instrumented, and user code was added, the user code would not always get linked into the instrumented harness executable. This has been fixed in VectorCAST version 6.4.6 and VectorCAST version 2018 SP3. 79227: Handle Ada compilers that elaborate function parameters out of order Previously, when instrumenting for MC/DC coverage, if a function call contained multiple parameters with boolean expressions, some compilers may have evaluated the subconditions out of order, resulting in incorrect coverage data. This problem has been fixed in VectorCAST version 6.4.6 and VectorCAST version 2018 SP3. VectorCAST/Analytics: 71516: Viewing original source in Analytics could give better error message when using MC/DC VectorCAST version 6.4.6 and VectorCAST version 2018 SP3 provide a better message when the user tries to view the Original Source Coverage report on a source file instrumented with MC/DC, which is not supported in Analytics. Additionally, the message remains visible until the user closes it. 74227: Cannot save Analytics configuration in Windows 10 for Edge and IE Previously, clicking the "Save Configuration (.vdash)" button did not work in certain browsers on Windows 10. This problem has been fixed in VectorCAST version 6.4.6 and VectorCAST version 2018 SP3. 76125: Repeated vcdash save history commands hang with '--include-source' Previously, VectorCAST would hang when executing an Analytics command involving '--include-source' similar to the following, twice: %VECTORCAST_DIR%\vcdash -p MyProject.vcm --history-dir=history --save-history --include- source This problem has been fixed in VectorCAST version 6.4.6 and VectorCAST version 2018 SP3. VectorCAST/C++: 72742: Test Tree missing subprograms when a template function has the same name and parameter profile as another non template function Previously, the test case tree omitted subprograms when a template function had the same name and parameter profile as another non template function in the same unit. This problem has been resolved in VectorCAST version 6.4.6 and VectorCAST version 2018 SP3. To get the new behavior, you must rebuild any affected environments. 74496: P-object for templated union or struct with no default constructor is not generated correctly Previously, VectorCAST did not generate test harness code properly for some testable functions with struct or union parameters having template constructors which are not instantiated, causing a compile error. This problem has been resolved in VectorCAST version 6.4.6 and VectorCAST version 2018 SP3. 74613: Function call coverage incorrectly affects statement coverage Previously, turning on function call coverage caused the line showing whether an empty constructor which calls a base class constructor is covered to be omitted from the aggregate coverage report when using statement+MC/DC or statement+branch coverage. For example, the listing file would display: Class::Class() { 1 0 ( ) Class::Class } with function call coverage on, but then display: Class::Class() { 1 0 ( ) Class::Class 1 1 } with function call coverage off. The number of covered statements in the metrics section was correct in both cases. This problem has been resolved in VectorCAST version 6.4.6 and VectorCAST version 2018 SP3. To get the new behavior, you must reinstrument any affected files. 75309: VectorCAST unnecessarily requires typeof operator for stubbing globals when volatile qualifier used in typedef'd structs+unions When the configuration option VCAST_TYPEOF_OPERATOR was set to false, VectorCAST omitted stubs for typedefed volatile structs and unions. This problem has been resolved in VectorCAST version 6.4.6 and VectorCAST version 2018 SP3. To get the new behavior, you must rebuild any affected environments. 76069: Crash building unit test environment for some classes with fields of std containers of themselves if std code is testable text goes hereVectorCAST crashed while building unit test environments for some classes with fields of std containers of themselves if std container code is in a testable directory. This problem has been resolved in VectorCAST version 6.4.6 and VectorCAST version 2018 SP3. 76481: Command 'clicast tools execute' can lead to link error when recompiling C++ environment Previously, running the clicast command "TOols EXEcute_commands" with a command file that includes commands with the language flag omitted or set to c instead of cplusplus for a C++ environment could cause subsequent environment recompilations to fail with a link error. The link error mentioned undefined references to VCAST_Get_CSU_Data and VCAST_Add_CSU_Data. This problem has been resolved in VectorCAST version 6.4.6 and VectorCAST version 2018 SP3. If you have existing environments where the recompile fails, rebuild the environment to avoid the problem. 77006: Recursive constructor call in expanded driver when a parameter name is not provided in a stubbed ctor VectorCAST now uses the automatically generated parameter name for unnamed parameters in constructor member initialization of stubs. This prevents some instances of infinite recursion when the stub is called during test execution. This problem is resolved in VectorCAST version 6.4.6 and VectorCAST version 2018 SP3. VectorCAST/Cover: 76166: Unable to generate the coupling coverage report if result files were split up during test execution Previously, when using the function VCAST_DUMP_COVERAGE_DATA(), VCAST_CLEAR_COVERAGE_DATA(), and Coupling in a Cover environment, VectorCAST did not properly dump and clear coupling data. The problem caused an error when trying to generate the Coupling Coverage report. These problems have been fixed in VectorCAST version 6.4.6 and VectorCAST version 2018 SP2. 76783: Coupling analysis leads to memory error Previously, under certain conditions, coupling analysis for large environments could lead to a crash. In VectorCAST version 6.4.6 and VectorCAST version 2018 SP3, memory consumption and performance has been improved for all coupling actions. To get the fixed behavior, perform coupling analysis and coupling apply again. 77047: Function calls with branches in logical operators are instrumented for MC/DC incorrectly When the configuration option VCAST_USE_OPTIMIZED_MCDC_INSTRUMENTATION was set to true, MC/DC instrumentation was incorrect for source code containing function calls inside logical operators if the function calls had parameters with additional branch conditions. The incorrect instrumentation resulted in invalid lines being reported when coverage results were added to a project, and the resulting coverage reports were incorrect. This problem has been resolved in VectorCAST version 6.4.6 and VectorCAST version 2018 SP3. 78553: Coupling Report Generation fails with Virtual Functions Previously, the coupling coverage report could not be generated when mangled c++ data couples were present. Mangled data couples can be introduced by having a data couple defined within a namespace. In VectorCAST version 6.4.6 and VectorCAST version 2018 SP3, the coupling coverage report can now be generated when mangled c++ data couples are present. 78604: Unit Test coupling data not produced with Coverage I/O set to Buffered Previously, when using Unit Test to generate coupling data, if the environment used Buffered I/O, no coverage data would be reported. This problem has been fixed in VectorCAST version 6.4.6 and VectorCAST version 2018 SP3. 78922: Coupling analysis fails when the needed file contains data couple references lacking the statement attributes Previously, when performing coupling analysis, a crash would occur if a data couple reference was encountered that is not considered a statement. One such example would be data couples referenced within the member initialization list of a constructor. In VectorCAST version 6.4.6 and VectorCAST version 2018 SP3, when these references are encountered they will be logged in the computeCouples.stdout.txt file and skipped. The skipped references will appear in the file in the following format: Skipped invalid reference: file: dcc_source_file.cpp line: 9 column: 22 79082: Add asterisk to covered control couples in the coverage report Previously, only covered data couples within the coupling coverage report were prefixed with the covered indicator, an asterisk (*). In VectorCAST version 6.4.6 and VectorCAST version 2018 SP3, covered parameter data couples and control couples are also prefixed using the covered indicator (*). 80349: Combine coverage from tests when determining whether or not a couple is covered Previously, when determining if a couple was fully covered, VectorCAST did not correctly combine results from separate test cases. Accessing a data couple in only one component for a test and then accessing it in another component for a different test was not reported as a covered couple. This problem is resolved in VectorCAST version 6.4.6 and VectorCAST version 2018 SP3. 79875: Improve handling of function pointers VectorCAST version 6.4.6 and VectorCAST version 2018 SP3 include improved analysis for