Release Notes - VectorCAST: 6.4x Known Issues: 61870: Exception not detected as an Expected Value with "Fail if no expected values" or "Fail empty testcases" set to True When using either of the Execution options "Fail empty testcases" or "Fail if no expected values" set to True, VectorCAST is incorrectly marking tests with Exceptions as an Expected Value as failed, when they should be marked as passing. The clicast options are: - VCAST_EMPTY_TESTCASE_FAIL - VCAST_TESTCASE_FAIL_ON_NO_EXPECTED
VectorCAST/C,C++, Ada (Core) 64712: Debug log empty unless viewed via "View Debug Log" button in Troubleshooting dialog Previously, when executing tests in the VectorCAST GUI using the Debug logging feature (accessed from Help => Troubleshooting => Diagnostics), the debug.log.gui file would be empty if the user viewed it without going back to the Debug dialog and clicking the "View Debug Log" button. In VectorCAST version 6.4x, the log can be viewed from a shell, via File => Open, or via the Troubleshooting dialog, and it contains the correct information.
VectorCAST/Ada: 63037: Renaming Ada environment made from 'gpr' file causes compile errors Previously, when working with a VectorCAST/Ada environment that was built with a GNAT .gpr file, selecting VectorCAST's File => Rename Environment menu item would cause failures when later compiling the harness (for user code or instrumentation). This problem has been fixed in VectorCAST version 6.4x. 64608: Stub-by-function for Ada does not work in subprograms that are 'separate' Previously, if a subprogram within a Unit Under Test was declared as 'separate' and the environment was built using Stub-By-Function, the 'separate' subprograms would appear as stub-able, but only the real subprogram was ever called. This problem has been fixed in
VectorCAST version 6.4x. 64699: Coverage report not showing correct unit information for generic instances Previously, when viewing a report containing coverage (Test Case Management, Aggregate Coverage, Metrics report), and a test case was selected in a UUT that is a generic instantiation, the report would not show any coverage (because the coverage is associated with the generic package, not the instantiation). This problem has been fixed in VectorCAST version 6.4x. 66096: Compiler complains about "ambiguous expression" when adding user code Previously, if the source under test did a "use ;" for a package that defined a subtype of boolean, then the compiler could generate an error for VectorCAST's test harness code that was included when Parameter User Code was added for a testcase. This problem has been resolved in VectorCAST version 6.4x. 66187: Very long lines possible in Ada harness for enumerated types Previously, when the fully qualified typemark for an enumerated type is very long, VectorCAST generated harness code with the typemark appearing on the same line, causing a source line with greater than 200 characters. For some compilers, this line length causes a compilation error. This problem has been fixed in VectorCAST version 6.4x.
VectorCAST/Analytics: 54513: Error message for errors on server startup Previously, the the Analytics server (vcdash) did not provide output when exiting due to Port or IP address conflicts. This problem has been fixed in VectorCAST version 6.4x. 64281: Ctrl+C no longer kills the Analytics server (vcdash) on Windows Previously, in some cases, when run from the Windows command prompt, the Analytics server (vcdash) would not shut down when sent CTRL+C. This problem has been fixed in VectorCAST version 6.4x, though it may take a few seconds for the server to shut down. On Windows, you can force the server to shut down immediately with CTRL+BREAK, but this method may leave some temporary files on your filesystem.
VectorCAST/C++:
61991: Update to character parameter data entry (GUI and scripting) Previously, setting String Display mode to Pointer and its Character Display mode to Character was incorrectly initializing its base type, resulting in character values being lost after the test case was saved or imported from test script. This problem has been resolved in VectorCAST version 6.4x. Users can expect the following behavior when entering values for a character parameter in the Parameter Tree: - If the entry is an alphabetic or special character, the parameter is switched to Character mode and the entry is displayed as a character. - If the entry is a hex or octal number, the parameter is switched to numeric mode and the appropriate base, and the entry is displayed in that base. - If the entry is a negative number, the parameter is switched to numeric mode and displayed as decimal. - If the entries for Input and Expected values are entered using different methods (mode and base), the parameter is switched to the second method used, causing both Input and Expected values to be displayed in the same mode. 62063: Incremental rebuild treats undeclared functions as new dependencies In previous versions of VectorCAST, calls to undeclared functions would always be treated as new dependencies when evaluating whether incremental rebuilds were possible. This problem is fixed in VectorCAST version 6.4x by ignoring undeclared functions when performing incremental rebuilds. 63226: Allow additional stubs in library test mode Beginning in VectorCAST version 6.4x, the ENVIRO.ADDITIONAL_STUB environment script command may now be used to specify functions which should be stubbed in library interface testing mode. The format is: ENVIRO.ADDITIONAL_STUB:
63274: Support Visual Studio 2017 VectorCAST version 6.4x adds support for Visual Studio 2017. To use Microsoft Visual Studio 2017, from the Windows Start menu, select All Programs
=> VectorCAST => VectorCAST for Visual Studio => VectorCAST for Visual Studio 2017. clicast -lc template VISUAL_CPP_2017 clicast -lc template VISUAL_CPP_CPP_2017
64105: Link error because array stub is a redeclaration not a definition when type is a typedefed unconstrained array Previously, VectorCAST re-declared undefined externs which were typedefed unconstrained arrays instead of defining them. For example, typedef unsigned char TYPEDEFED_UNC_ARRAY[]; extern TYPEDEFED_UNC_ARRAY foo;
would result in an environment that did not link. This problem has been resolved in VectorCAST version 6.4x. To get the new behavior, you must rebuild any affected environments. 64112: Using environment variable in testable, type-handled, or library include directory causes extra error message in parse error Previously, use of an environment variable when specifying a testable, type-handled, or library include directory could result in a message stating that the environment variable was not found (despite the environment variable being set) during environment build on the Linux and Solaris platforms if the source code did not parse for other reasons. This problem has been resolved in VectorCAST version 6.4x. 64467: Instrumented files appending cover I/O not touched when vcast_c_options. h changes from GUI starting with version 6.4s VectorCAST versions 6.4s and later did not update the modification time of instrumented files appending cover I/O when other files were instrumented from the GUI, even if the files were inside the environment directory. This problem has been resolved in VectorCAST version 6.4x. 64516: Concrete class stub incorrectly uses forward declared struct or union in subsequent units Previously, when the configuration option VCAST_AUTO_CONCRETE_CLASS_GENERATION was set to true, the environment that was generated for source code with an abstract struct definition in one unit and a forward declaration of that struct in a subsequent unit where a stub for a function taking a reference to the struct was needed did not compile.
This problem has been resolved in VectorCAST version 6.4x. To get the new behavior, you must rebuild any affected environments. 64539: Incorrect generation of object file testing interface file when global array has a name in parentheses In previous versions of VectorCAST, when using Object File Testing mode, the environment did not compile if a source file contained a global array variable with the array name in parentheses, such as: int (array_name)[2];
This problem has been resolved in VectorCAST version 6.4x. 65149: Configure stubs user code not automatically compiled into instrumented harness when coverage enabled with version 6.4s and later VectorCAST versions 6.4s and later did not automatically compile configure stubs user code into the instrumented harness. This problem has been resolved in VectorCAST version 6.4x. 65391: Parse error when designated initializer used for parameter of reference type Previously, VectorCAST incorrectly gave the error "no instance of overloaded function matches the argument list" when source code contained a designated initializer for a parameter of reference type. For example: struct S { int i, j; }; void f(S&&) {} int main() { f({.i = 1, .j = 2}); // Previously an error. Now okay. }
This problem has been resolved in VectorCAST version 6.4x. 65481: Coverage instrumentation inserted in invalid location if preceded by basis path analysis Previously, when doing basis path analysis and then instrumenting a C source file with the configuration option VCAST_COVERAGE_FOR_DECLARATIONS set to true, VectorCAST would sometimes insert a right parenthesis in an invalid location if the first variable initialization in a function contained an enumeral. This problem has been resolved in VectorCAST version 6.4x.
65540: Test harness should use ::delete when calling testable destructors Previously, the test harness might not compile when building an environment for source code containing a class that defined an overloaded delete operator. This problem has been resolved in VectorCAST version 6.4x by using ::delete to avoid use of the overloaded delete.
VectorCAST/C++ and VectorCAST/Cover: 66044: CBA adds coverage to unchecked lines when saving changes if blockcoverage is enabled Previously, when using the option "Instrument blocks for statement coverage" with Statement+MC/DC coverage, after adding some Coverage By Analysis in the Editor, the Editor would incorrectly mark additional lines with CBA checkmarks upon saving. This problem has been fixed in VectorCAST version 6.4x.
VectorCAST/Cover: 62514: Invalid Branch instrumentation inserted for expression of overloaded operator && Previously, VectorCAST generated instrumentation code that did not compile when C++ source code contained any of the following functions (if those functions returned class values): operator operator operator operator operator operator operator operator operator
&& || ! == != > >= < <=
The problem occurred because VectorCAST treated the functions the same as comparison operators. In VectorCAST version 6.4x, VectorCAST treats the functions as if they were the same as comparison operators if the functions return bool or integer values, and if the new configuration option VCAST_COVER_OVERLOADED_LOGICAL_OPERATORS is set to True. The option is set using clicast only.
When the option is False, VectorCAST does not treat the functions as comparison operators, and therefore does not consider calls to those functions to be branches. clicast -lc option VCAST_COVER_OVERLOADED_LOGICAL_OPERATORS True | False
The default value is True. 64148: Error seen when compiling coupling-instrumented source file in certain case Previously, coupling instrumentation of C source files placed executable statements before variable declarations, causing compile errors for some compilers. This problem has been resolved in VectorCAST version 6.4x. You must re-create the Cover environment to get the new behavior. 64297: Coverage instrumentation added to enum definition Previously, VectorCAST added Branch instrumentation inside enum definitions containing the "?" operator if the enum value was used later in a branch statement. The instrumentation inside the enum definition did not compile. Also, Basis Path and MC/DC Test reports showed incorrect branches inside the enum definition. These problems have been resolved in VectorCAST version 6.4x. 65889: Branch coverage incorrectly handles nested switch statements in 6.4r and later when CASE_FALLTHROUGH_BRANCH_COVERAGE is false When CASE_FALLTHROUGH_BRANCH_COVERAGE is set to False and Branch coverage is initialized, case statements in a switch statement following a nested switch statement reached without fallthrough were not recorded as covered if the nested switch was entered. This problem has been resolved in VectorCAST version 6.4x.
VectorCAST/Manage: 64633: Default options that are explicitly set were ignored when migrating Previously, when a monitored environment was built with a default value for a configuration option (such as C_COMPILER_CMD), the option would not be imported during migration if the same option was set with a custom value at a higher node in the Manage Project Tree. VectorCAST version 6.4x correctly uses a default value for an option that has been explicitly set prior to migrating an environment. 64759: CBA is not retained on Incremental Rebuild for Unit Monitored envs Previously, a monitored Unit test environment would lose CBA coverage after an Incremental Rebuild. This problem has been fixed in VectorCAST version 6.4x.
VectorCAST/RSP: 34658: RSP for Green Hills MIPS INTEGRITY 178B for Ada VectorCAST/Ada version 6.4x now supports the Green Hills MIPS Integrity 178B target. To use this licensed RSP, select File => New => Ada Target Environment => MIPS Green Hills Integrity. clicast -lada -x MIPS_GH_INTEGRITY env build
63495: mwccs12lisa requires support for binary constants Previously, when using codewarrior versions hc12 and hcs08, and code containing binary constants, it would cause a parse failure and generate an error. This is resolved in VectorCAST version 6.4x. 63943: Static memory with Ada configurable I/O does not work correctly with MC/ DC coverage Previously, when using the Ada configurable I/O method of target execution with static memory management and MC/DC coverage, the harness could crash with a memory violation when a subcondition was hit multiple times. This issue has been fixed in VectorCAST version 6.4x. 64631: Intex failure should halt test execution Previously, VectorCAST would not always detect when a Green Hills intex command failed. This could cause VectorCAST to execute the wrong test harness. This problem is fixed in VectorCAST version 6.4x. 64882: EDG parser reports "error: struct or union is too large" with keil compiler Previously, VectorCAST incorrectly reported "error: struct or union is too large" for some large array fields when the Keil compiler was selected. This problem has been resolved in VectorCAST version 6.4x.
Release Notes - VectorCAST: 6.4w VectorCAST/C,C++, Ada (Core) 63992: Open html help locks current directory preventing rebuild
Previously, when the user tried to rebuild an environment while an HTML or PDF user guide was open, an error occurred saying that VectorCAST could not backup the directory. This problem has been fixed in VectorCAST version 6.4w. 64204: Compound test cases always fail when "Fail if no expected values" option is set Previously, when the option "Fail if no expected values" was True, a Compound testcase would fail when the user initiated test execution (without actually executing) because a Compound testcase has no expected values itself, only its slots do. In VectorCAST version 6.4w, executing a Compound testcase honors the option correctly by failing after execution if no Expected values are present in any slot. 65019: Ignore invalid tu position in coverage database Beginning in VectorCAST version 6.4u, an issue in the coverage database caused environment re_build to hang. This issue has been fixed in VectorCAST version 6.4w.
VectorCAST/Ada: 63548: Harness build error when nested instantiation textually matches child packagename When a nested generic instantiation inside a child package uses a package name that contains part of an ancestor parent name, VectorCAST can incorrectly assume types are visible when they are not, causing harness compilation errors. This has been resolved in VectorCAST version 6.4w. 64110: Typemark defined solely in the private section of a parent unit can cause harness compilation errors Previously, when a tagged type was defined solely in the private section of a unit, and a child of that unit referenced a typemark that included a type derived from the tagged type, when building a multiunit whitebox environment VectorCAST would incorrectly try to call a procedure in the parent unit from the child unit that was not visible. This has been resolved in VectorCAST version 6.4w. 64635: Preprocess GNAT files not working correctly when object directory is different than source directory Previously, when building an Ada environment with GNAT, and the option 'Preprocess GNAT source files' flag is set, if the GPR file specified an Object directory that was
different than the Source files location, the preprocess would fail and VectorCAST would use the un-preprocessed file. This problem has been fixed in VectorCAST version 6.4w. clicast -lada VCAST_PREPROCESS_ADA_FILES True | False
The default value is False.
VectorCAST/Analytics: 64416: Analytics file viewer, long file paths are truncated at the start of path Previously, long file paths would not display properly in the Analytics file viewer. In VectorCAST version 6.4w, if the file path is too long to display the complete path, it is truncated at the start of the path with ellipsis.
VectorCAST/C++: 56040: std::list and std::string not detected when using g++ 5+ C++11 Some versions of g++ first define std::list and std::string as std::__cxx11::list and std::__cxx11::string respectively when C++11 is in use. Previous versions of VectorCAST would fail to detect these as the standard list and string types. This problem is fixed in VectorCAST version 6.4w. 57005: New option VCAST_TEST_UNIT_USER_CODE to control whether user code functions are testable "Consider unit user code functions testable" is a new option available in VectorCAST version 6.4w to control whether functions defined in unit appendix and unit prefix user code show as testable in the test case tree. Note that regardless of the value of this option, such functions do not get instrumented for coverage or SBF stubbing. clicast -lc option VCAST_TEST_UNIT_USER_CODE TRUE|FALSE
62931: Function under test taking a non-copyable parameter within a std container is not suppressed Previously, the test harness for functions with parameters that are std containers of noncopyable types did not compile. This problem has been resolved in VectorCAST version 6.4w. To get the new behavior, you must rebuild any affected environments. 63204: Test Execution issues using % char (\045) as input to std::string Previously, VectorCAST crashed when a string was input with \045 as the last character.
This problem is fixed in VectorCAST version 6.4w. 63225: Additional Stubs take precedence over Suppressed stubs The VectorCAST environment wizard allows specifying Additional Stubs and Suppressed Stubs. In previous versions of VectorCAST, if a function matched an entry in both lists, the suppression would take precedence. In VectorCAST version 6.4w, the addition takes precedence. 63788: TI shared across units even though field is a type where the set of subclasses differs across units Previously, when the environment variable VCAST_TI_NO_COMMON_TYPE_SUPPORT was not set, VectorCAST used a type handling function from one unit in other units, despite the subclasses for the types differing. The call to the incorrect function could result in the wrong subclass being selected during test execution. This problem has been resolved in VectorCAST version 6.4w. To get the new behavior, you must rebuild any affected environments. 63839: Probe point can't be applied to overloaded function Previously, VectorCAST allowed probe points to be specified within overloaded functions, but would not actually insert the probe point code into the overloaded function code. This problem has been fixed in VectorCAST version 6.4w. 64029: structs without member functions do not show inherited functions in test tree Previously, inherited member functions of structs without their own member functions were not testable. This problem has been resolved in VectorCAST version 6.4w. To get the new behavior, you must rebuild any affected environments. 64224: Functions with std::unique_ptr arguments not testable Functions with std::unique_ptr arguments were not testable. This problem has been resolved in VectorCAST version 6.4w. To get the new behavior, you must rebuild any affected environments.
VectorCAST/C++ and VectorCAST/Cover: 62362: Clicast interface to Probe Points database via serial numbers (IDs)
VectorCAST version 6.4w supports the ability to identify individual probe points by a serial number or ID. This functionality is implemented via three new CLICAST commands to enable, disable, or remove a specific probe point. Upon creation of a probe point in the GUI or via CLICAST, the probe point is assigned a serial number or ID. The first probe point is assigned the number 1 by default, unless the probe point was added via CLICAST using the text: PROBE_ID:
positioned after the definition of the probe point in the .env script or probe point file. If two probe points are given the same ID, the second one encountered is given the next available ID number that is unique. When a probe point is deleted or dropped due to changes in the source code, its ID is deleted also, and can be re-used for another probe point. The IDs are displayed in the Probe Point Listing report (GUI) and in the XML report (CLICAST). To add a probe point: clicast -e TOols PRobe_point ADD_file clicast -e Cover PROBE_point ADD_file
New commands to enable, disable, or remove a specific probe point: clicast -e TOols PRobe_point DISable_id clicast -e TOols PRobe_point ENAble_id clicast -e TOols PRobe_point REMOVE_Id clicast -e Cover PROBE_point DISable_id clicast -e Cover PROBE_point ENAble_id clicast -e Cover PROBE_point REMOVE_Id
When one of the above commands is run to enable, disable, or remove a probe point via ID, it is merely scheduled to have that action occur. The action takes place when the Apply command is run. If the environment is opened in the GUI before Apply has been performed, it is recommended that Apply be immediately performed by clicking the "Not Applied" button in the Probe Point Editor. clicast -e TOols PRobe_point APPly clicast -e Cover PROBE_point APPly
VectorCAST/Cover:
51609: VectorCAST component editor VectorCAST version 6.4w includes a new component editor. The component editor provides an easy to use GUI interface and allows the user to create and configure the components for coupling analysis. The following new commands are now available from the Cover Project Tools Menu: - Tools => Coupling => Components => Generate This generates a default set of components based on the source directory structure. Each directory creates a new component. This is equivalent to the clicast command: clicast -lc -e COUpling COMponents
- Tools => Coupling => Components => Edit This opens the component editor GUI and allows the user to modify the component configuration and move files between components, create new components, and remove existing components. - Tools => Coupling => Analyze This performs coupling analysis and is the equivalent to the clicast command: clicast -lc -e COUpling ANalyze
- Tools => Coupling => Apply This adds the function calls necessary to gather control coupling data during execution and is equivalent to the clicast command: clicast -lc -e COUpling APply
- Tools => Coupling => Generate Coverage Report Generates the Coupling Coverage Report and is equivalent to the clicast command: clicast -lc -e COUpling REport COUples
62839: Improve Support for Control Coupling via Function Pointers VectorCAST version 6.4w adds support for handling function pointers involved in Data and Control Coupling. In previous versions, the Coupling Coverage Report indicated that calls via function pointers had been detected and needed analysis. VectorCAST provides a mechanism for the user to do manual analysis of each call via function pointer, the outcome of which then indicates to VectorCAST which functions their application might call on that line of source code. VectorCAST then “reads” that information before doing the Coupling Apply (instrumentation). Two new CLICAST commands are supplied to perform the manual analysis.
1. Run clicast -e COUpling ANalyze [] 2. If a function pointer is detected and displayed in the output, run clicast -e COUpling MAnual_analysis GEnerate_report 3. The output in lists each call via function pointer, the unit name, the line
and column where it is called, and the word "analyze". It is up to the user to change the word "analyze" to either "ignore" or "active". - Enter "ignore" if the call via function pointer does not actually call any function involved in a data or control couple. An example of a function pointer call that can be ignored is a call to a function that wraps a call to a standard library function created specifically for your target. - Enter "active" if the call via function pointer is involved in a data or control couple. Each line with "active" also requires that the field "fp-targets" have a space-separated list of function names in your code that this line could possibly call. 4. Once this information is provided in and saved, call this CLICAST command to instruct VectorCAST on how you want the function pointers handled: clicast -e COUpling MAnual_analysis UPdate
Continue on as usual, running the Coupling Apply command.
VectorCAST/Manage: 52067: Manage is not aware of Industry Mode when selecting Code Coverage Previously, when VectorCAST/Manage was set to an industry mode other than default, the coverage type configured displayed the description associated with "default industry mode". In VectorCAST version 6.4w, the coverage type corresponds to the industry mode configured. If a coverage type does not exist for a particular industry mode, the description from default industry mode will be used. 63596: Manage/QA build/execute preserves CBA Previously, when performing a build/execute on a Manage/QA environment that contained CBA results, the CBA information would be lost. This has been fixed in VectorCAST version 6.4w.
VectorCAST/RSP: 62705: Parser should allow indexing into char literals in --tasking mode Tasking compilers allow indexing into multi-byte char literals, as in: return 'abcdefgh'[index];
Previous versions of VectorCAST issued an error when parsing this code in tasking mode. This problem has been fixed in VectorCAST version 6.4w.
Release Notes - VectorCAST: 6.4v VectorCAST/C,C++, Ada (Core) 49474: Allow monitored VC/Cover environments to be created from VC/Manage VectorCAST version 6.4v now includes the shortcut to create a new, monitored, Cover environment within your VectorCAST/Manage project. By default, the environment is stored in vcast_qa sub-folder within the work space directory, but can be modified by the user by setting the "Storage Location" in the environment wizard. 55148: Support for Saving Coverage Reports to any filename and extension Previously, the user wanting to save all coverage reports via the Save Coverage Reports dialog was restricted to selecting only the location in which the reports would be saved. Each report was saved with a hard-coded name in the format: __report.html or .txt
The dialog did not allow the user to specify a filename and file extension for the reports. In addition to the existing functionality, in VectorCAST version 6.4v the user can choose to save a single report to any location, filename, and file extension. The report must be in TEXT format to enable this selection. As before, the user sets the checkboxes to specify which sections to include in the combined report. The data for all selected units are combined into a single report To access the Save Coverage Reports dialog in a Cover environment: 1. Select the unit(s) you want to include in the report. 2. Choose Environment => View => Save Coverage Reports... In a Unit Test environment: 1. Select the unit(s) you want to include in the report. 2. Choose Test => Save Coverage Reports... 59181: Update Japanese and Chinese translations
VectorCAST version 6.4v includes updated translations for Japanese and Chinese languages. 60689: Crash using F5 while renaming a test case Previously, VectorCAST permitted test execution to be started using F5 even when a test was in rename mode. This situation caused the execution to continue indefinitely, appearing as though the GUI crashed. This problem has been resolved in VectorCAST version 6.4v. 60929: VectorCAST should set LM_APP_DISABLE_CACHE_READ if VECTOR_LICENSE_FILE or LM_LICENSE_FILE is set In VectorCAST version 6.4v, if the VectorCAST license is defined by the environment value VECTOR_LICENSE_FILE or LM_LICENSE_FILE, VectorCAST will ignore the value defined in the registry. To use the registry value, unset the environment variable(s). 62628: Add support for maintaining test script when functions move from one UUT to another Previously, when a subprogram was moved from one UUT to another, the Test Script Maintenance utility would not be able to identify that the testcases were still applicable to the environment, just in a different unit. As a result, the testcases were removed from the environment on test script re-import. In VectorCAST version 6.4v, the Test Script Maintenance utility correctly assigns the testcases for the moved subprogram to the other unit. 63113: User action before re-build is finished VectorCAST version 6.4v contains fixes for GUI crashes that can occur when using the environment wizard or when rebuilding environment. 63146: Test Case Maintenance Utility takes 30-40 minutes Previously, when rebuilding an environment, the Test Script Maintenance Utility took a long time when the size of the environment artifacts exceeded a certain size. In VectorCAST version 6.4v, the behavior of the Test Script Maintenance Utility has been altered to support this use-case more efficiently. 63355: When using VectorCAST in Japanese, dialog boxes and Manage configuration tooltips have garbage characters
Previously, when using the VectorCAST GUI with the Japanese language selected, the Help About dialog and the Instrumentation progress dialog contained unprintable or "garbage" characters. In addition, in Manage, some tooltips in the Configuration window also contained garbage characters. These problems have been resolved in VectorCAST version 6.4v. 63517: Improve diff processing for Test Script Maintenance Utility Previously, when rebuilding an environment, the Test Script Maintenance Utility took a long time when the testcases in the environment contained a very large set of values. This problem has been mitigated in VectorCAST version 6.4v. 63537: Partition tests generated without range data fail to execute Previously, when the clicast command "test partition" was run with no range data available, VectorCAST would indicate the tests were created, but the internal data structures were not populated correctly. This caused a crash when those tests were executed. Starting with VectorCAST version 6.4v, trying to generate partition test cases without range data will result in an error message. 64023: Debug mode enabled in Licensing code VectorCAST version 6.4v supports tracking calls to VectorCAST's licensing functionality (FLEXlm) when in debug mode, specifically with vresult_trace enabled. 64215: Allow Coverage-By-Analysis results to be editable after import Previously, VectorCAST would not allow users to edit Coverage-By-Analysis (CBA) results via the CBA editor in the GUI that were imported from a coverage script (.cvr). VectorCAST version 6.4v allows all CBA results to be edited regardless of how they were created. This includes CBA results that were imported via .cvr, .cba, and after rebuilding an environment.
VectorCAST/Ada: 63361: Support for preprocessing Ada files when using GNAT GPR build process Previously, when VectorCAST encountered preprocessor directives in a source file, it would treat that line as a comment and ignore it. This could cause instrumentation issues because comments are stripped out of the instrumented file, which could cause incorrect behavior and/or coverage numbers. In VectorCAST version 6.4v, there is a new Builder option "Preprocess GNAT source files"
that enables preprocessing of the Unit Under Test (and any non-stubbed unit instrumented for code coverage) when the preprocessor is configured in the GNAT Project file (.gpr) specified when building the environment. clicast -lada VCAST_PREPROCESS_ADA_FILES True | False
The default value is False.
VectorCAST/Analytics: 62935: Data API delete speed Projects with very large numbers of iterations, range iterations, or tests may have experienced slow removal of test results. The issue causing this is now fixed in VectorCAST version 6.4v. Some data must be migrated into a new format for the fix, so if you are opening one of these projects for the first time after the update, you may experience a long delay. If you do not want to wait, you can skip this migration process by rebuilding your environment. 63307: Vcdash shows instrumented file VectorCAST version 6.4v fixes an issue that caused Analytics to display instrumented source files instead of original source files when using --history-dir and instrument-inplace.
VectorCAST/C++: 55668: Parser thinks more than one overloaded function matches argument list when using boost/signals2.hpp Previously, when parsing source code with a #include of boost/signals2.hpp, VectorCAST incorrectly gave the error: "more than one instance of overloaded function "boost::variant::initializer::initialize [with T0_=boost::weak_ptr, TN=, boost::signals2:: detail::foreign_void_weak_ptr>]" matches the argument list"
This problem has been resolved in VectorCAST version 6.4v. 59443: Char values rejected from .tst import after range collection failure In previous versions of VectorCAST, if an error occurred during range data collection, a test script import error would occur for test cases that specified character values. This problem is fixed in VectorCAST version 6.4v.
60551: Harness uses incorrect sprintf format string for double In previous versions of VectorCAST, the harness used a non-standard sprintf format string when printing values of type double. In VectorCAST version 6.4v, the standard "% g" format string is used. 61826: SBF code generates locally undefined Init Object, causing link error Previously, environments where a stub-by-function unit contained a testable function with a parameter that is an array of classes without default constructors did not link. This problem has been resolved in VectorCAST version 6.4v. To get the new behavior, you must rebuild any affected older environments. 62141: Compile error caused during Incremental Rebuild for an SBF unit with main Previously, incrementally rebuilding an environment with a stub-by-function unit containing the main function caused a compile error. This problem has been resolved in VectorCAST version 6.4v. 62714: Deactivated probe point missing from editor In previous versions of VectorCAST, deactivating all probe points after trying to apply a probe point with an error might cause the deactivated probe points to be missing in the probe point editor and/or report. This problem has been fixed in VectorCAST version 6.4v. 62963: Instrumented ternary operator where the second operand is omitted results in an incorrect value being returned Previously, branch or basis path instrumentation of a conditional operator with an omitted second operand caused 1 to be returned when the first operand evaluated to true. That behavior was incorrect when the first operand was a value other than 1. This problem has been resolved in VectorCAST version 6.4v. 63039: C/C++ Tutorial files now support Targets with no Standard Input In VectorCAST version 6.4v, the Tutorial files in the VectorCAST installation directory have been changed to allow users on Targets without Standard Input (stdin) to use them more easily. By default, the manager_driver.c (.cpp) source file requires stdin in its use of scanf (). However, when an environment is built with one of the following macros defined, the source file no longer requires stdin.
- If ORDER is defined while a UNIT TEST environment is built or instrumented or while a COVER environment is instrumented, then it is as if "P" (for Place_Order) has been entered as input. - If CHECK is defined, then it is as if "G" (for Get_Check_Total) has been entered as input. In addition, a script named buildIt is provided in the same directory. The script contains two ways to compile the sources. By default, it compiles the sources assuming stdin is available. By uncommenting the other command and commenting out the original command, the user can build the sources while defining ORDER. Note, to use the buildIt script with a COVER environment, the best practice is to append the c_cover_io.c file to one of the units, such as manager_driver.c (.cpp). To do this in the VectorCAST GUI, right-click manager_driver.c (.cpp) and choose "Append Cover IO". In CLICAST, enter either: clicast -e -u manager_driver.c cover append_cover_io True
or clicast -e -u manager_driver.cpp cover append_cover_io True
63200: Execution report generation now uses less RAM Previously, generation of execution reports failed for some large compound tests since VectorCAST ran out of memory. In VectorCAST version 6.4v, generation of text reports now uses less RAM. 63299: Pure virtual function overridden twice in generated concrete subclass Previously, when an abstract class contained a pure virtual function with the same name and parameters but a different return type as a pure virtual function in a base class, VectorCAST incorrectly generated definitions for both of those functions, causing a compile error. This problem has been resolved in VectorCAST version 6.4v. 64382: Stubbed constructor member initialization list should utilize pointers and references to abstract types VectorCAST version 6.4v is able to use the "this" pointer and parameters more often in the member initialization list of stubbed constructors. This usage should avoid situations where infinite recursion occurs due to the stub calling itself or other constructors. To get the new behavior, you must rebuild any affected environments.
VectorCAST/Cover: 62629: Incorrect instrumentation when local variable assigned constant bool
expression Previously, when instrumenting Statement+Branch coverage, the function's entry point coverage was missing when the first variable in the function was assigned the value of a constant expression containing a logical or comparison operator. Consequently, this statement with the constant was also missing coverage. For example, with source code like this: int func ( void ) { int local_variable = (0 != 0); return local_variable; }
the entry point to the function func did not receive coverage after test execution, and the line "int local_variable = (0 != 0);" was not instrumented. This problem has been fixed in VectorCAST version 6.4v. 62711: Call coverage result lines rejected when adding result file Previously when re-instrumenting with Function Call coverage enabled, VectorCAST would not correctly update the Function Call coverage stored in the database, which could result in invalid lines when adding result files. This problem has been corrected in VectorCAST version 6.4v so that the Function Call coverage is always updated when necessary. 63535: Crash instrumenting MC/DC or determining basis paths for certain source with Visual Studio C++ 2015 (6.4f and later) VectorCAST versions 6.4f and later crashed when initializing MC/DC coverage or determining basis paths for some Microsoft Visual Studio C++ 2015 code. This problem has been resolved in VectorCAST version 6.4v. 62742: Include Coverage-by-Analysis (CBA) data in Function Coverage Previously, VectorCAST would only consider run-time coverage (that is, coverage from test execution) and not Coverage-by-Analysis (CBA) as contributing toward function coverage. Function coverage is displayed as an additional column in the Metrics report and the Function Call Coverage report. In VectorCAST version 6.4v, this behavior has been changed so that both test execution coverage and CBA coverage contribute toward function coverage. Metrics Report
The Function Coverage column in the Metrics report displays "100%" if the function has been entered by either execution or CBA coverage. The two rows below that indicate how many statements are coverage by execution, and how many by Analysis. Function Call Coverage Report The Function Call Coverage report includes columns for both Function Coverage (the function has been entered) and Function Calls (the call has been executed). In VectorCAST, CBA data only affects function coverage, not function call coverage. When only CBA results are responsible for the function coverage, the character "A" (for "Analysis") is displayed in the Function Coverage column. When execution results or a combination of execution and CBA results contribute to the coverage, the usual "Y" (for "Yes") is displayed in the column. 63536: Preprocess or parse errors while instrumenting in a cover environment should be saved to unitname.ERR file Previously, preprocess or parse errors that occurred during instrumentation were written to the file VCAST.ERR, which was then overwritten when another unit had an error. This problem is resolved in VectorCAST version 6.4v, where errors for each unit are saved to an individual .ERR file. If instrumentation is successful, no .ERR file is created. 64175: CLICAST should report error file name during instrumentation when error is less than 6 lines long Previously, CLICAST did not report the name of the error file where a preprocess or parse error is logged if the error was less than six lines long. In VectorCAST version 6.4v, the name of the file is now given.
VectorCAST/Manage: 62097: Test script conversion failure triggers error 'Dependency Added, Full Rebuild Required' In previous versions of VectorCAST/Manage, the build and execution of an environment would be aborted after a tst script conversion failure. This has been resolved in VectorCAST version 6.4v. 62956: Output from the system_tests.py should go to the execute or build log
Previously, when python scripts were invoked by VectorCAST, stdout and stderr were directed to the debug stream. From CLICAST, output was directed to stdout and from the GUI, output was directed to the Message Window. In VectorCAST version 6.4v, python output is directed to the output handle at the time of invocation. For example, python output goes to the build.log when invoked during a build, or goes to the execute.log when invoked during execution.
VectorCAST/Probe: 61564: If I omit the trailing colon on a command, we get a STORAGE_ERROR to the console Previously, VectorCAST would fail to parse probe points added to the environment using a Probe Point file (.pp) containing a command without a trailing colon, causing the CLICAST command to hang or add invalid Probe Points. This problem has been fixed in VectorCAST version 6.4v. 63220: Adding probes using a .pp file may hang the parser Previously, VectorCAST would fail to parse probe points added to the environment using a Probe Point file (.pp) containing a blank line, causing the CLICAST command to add the Probe Point to hang. This problem has been fixed in VectorCAST version 6.4v.
VectorCAST/RGW: 58313: Intland Codebeamer RGW integration VectorCAST version 6.4v includes RGW support for Inland Codebeamer. Inland Codebeamer is a collaborative web-based requirements and ALM solution. The VectorCAST/RGW integration allows the user to import Requirements from the Codebeamer server, then export test results back to the Codebeamer server.
VectorCAST/RSP: 62383: Support 'Direct Array Indexing' on all Ada targets Previously, on certain limited Ada targets, VectorCAST was unable to determine the proper indices for arrays, and therefore only supported positional notation (1..N) instead of the actual array index. In VectorCAST version 6.4v, a new Builder option named "Alternate direct array
indexing" has been added to address this deficiency. When this option is True, VectorCAST builds the harness using a different mechanism which allows VectorCAST to get the appropriate index for almost every array, regardless of target limitations. clicast -lada option VCAST_TARGET_DIRECT_ARRAY_INDEXING True | False
The default value is False.
Release Notes - VectorCAST: 6.4u VectorCAST C,C++, Ada (Core) 60161: Failed to execute external editor command In the Options dialog, the user can specify a path to an External Editor to be used when opening text files. If the path contains spaces, the user encloses the path in quotes. Previous versions of VectorCAST incorrectly marked such a path in quotes as being in an error state, with a red outline, and would not start the External Editor. This problem has been resolved in VectorCAST version 6.4u. 61940: Saving Code Coverage Summary does not honor VCAST_RPTS_DELIMITER option Previously, when saving the Code Coverage Summary report from the GUI as a .CSV file, the column separator was a "," which could cause parsing errors if the subprogram name also contains "," (for overloaded subprograms). Additionally, the option "Delimiter" on the Reports tab, Format sub-tab, Text sub-sub-tab was not being honored when saving the Code Coverage Summary. In VectorCAST version 6.4u, VectorCAST honors the VCAST_RPTS_DELIMITER option as a column separator when saving the Code Coverage Summary. 62646: Crash when saving testcase while selected in Execute Status details Previously, a crash occurred while saving a test case with results and coverage after that test case was selected in the Execution Status window. This problem has been fixed in VectorCAST version 6.4u. 62877: Easy way to copy info from About VectorCAST dialog to clipboard In VectorCAST version 6.4u, in the About VectorCAST dialog, text can be selected with the mouse and copied to the clipboard using the right-click menu or the Ctrl+C shortcut.
62886: Button to move units in Create Environment wizard is disabled Previously, in VectorCAST version 6.4t, the controls to add and remove units in the Create Environment wizard's "Choose UUTs & Stubs" step were disabled inappropriately. This issue has been fixed in VectorCAST version 6.4u.
VectorCAST/Ada: 47400: Pragma Unreferenced causes compile error in SBF Previously, if a subprogram in a Unit Under Test used 'pragma unreferenced', building a Stub-By-Function environment for that unit would generate a compile error due to the parameter being referenced as part of the stub processing. This has been fixed in VectorCAST version 6.4u. 62355: Global anonymous array objects defined after a nested package cause harness build error Previously, if a Unit Under Test contained a global anonymous array, such as: OBJECT : array ( 1 .. N ) of TYPE_T;
that was defined after a nested package body, VectorCAST's harness code inserted into the nested package body would incorrectly refer to the global object, causing compilation errors. This problem has been resolved in VectorCAST version 6.4u. 62631: Typemark containing private types from nested package causes harness compilation error Previously, when a Unit Under Test contained a typemark that referred to a private type within a nested package (e.g. an array whose element was a private type), VectorCAST's harness code inserted into the top-level package would incorrectly refer to a non-visible procedure within the nested package, causing compilation errors. This problem has been resolved in VectorCAST version 6.4u. 62694: Compilation error when UUT is instance of nested generic package Previously, when a Unit Under Test was an instantiation of a nested package, and that nested package defined its own types, VectorCAST could incorrectly build the test harness, resulting in error messages indicating a typemark was not visible. This problem has been fixed in VectorCAST version 6.4u.
VectorCAST/C++:
39195: Improved preservation of CBA data across source code changes Previously, when rebuilding an environment with Coverage By Analysis data (CBA), VectorCAST would retain the CBA in unpredictable and sometimes incorrect ways. For example, if a source code line with CBA was modified and the environment rebuilt, the line would still (erroneously) be covered by CBA. Similarly, if a new line of code was inserted in a function above the CBA-covered line and the environment rebuilt, a different line would be (erroneously) covered by CBA. In VectorCAST version 6.4u, CBA is preserved across source code changes in a predictable manner. During environment rebuild, VectorCAST exports the CBA data to a .cvr script with 2 lines of context before and/or after the line with CBA. If any of these lines have changed in the source code, the CBA is discarded and noted in the Coverage Import/Export Log. A current limitation of this feature in VectorCAST version 6.4u is that the Import Log is not displayed in the GUI or in CLICAST when CBA data is removed after environment rebuild. - This log can be accessed in the GUI using the Coverage => View Import Log menu item. - To see the Import Log after rebuilding the environment in CLICAST, look at the file IMPORT.LOG in the environment directory. 43013: Allow increment/decrement on enums in Borland mode Previously, using increment/decrement on enums with Borland mode in a Unit test environment would cause a parser error. This problem has been resolved in VectorCAST version 6.4u. 43721: Variables named f in test harness renamed to vcast_f Previously, the test harness used some variables named f. In VectorCAST version 6.4u, those variables have been renamed to vcast_f so that users who need to #define f for their source code may do so. 52004: Stub generated for function which cannot copy its return type Previously, stubs were incorrectly generated for functions where the return type had a private or protected copy constructor, causing a compile error. This problem has been resolved in VectorCAST version 6.4u.
57368: Function which returns private type treated as uncallable/untestable Functions returning private or protected types were previously not testable. In VectorCAST version 6.4u, new environments allow testing of those functions, though the returned value cannot be captured. 60627: Array of anonymous struct incorrectly stubbed Previously, stubs for arrays and pointers to anonymous classes, structs, and unions had incorrect syntax, causing compile errors. In VectorCAST version 6.4u, anonymous classes, structs, and unions are now stubbed correctly if C++11 is available, or if the new Build option VCAST_TYPEOF_OPERATOR is set to True. clicast -lc option VCAST_TYPEOF_OPERATOR True | False
The default value is determined by the compiler template. This option indicates whether the compiler accepts the __typeof__ operator. 61648: Coverage instrumenter should not treat unique symbols as being defined at unique addresses Previously, branch conditions that compared weak symbol pointers could incorrectly be treated as constant. This problem is resolved in VectorCAST version 6.4u, where the branch instrumentation allows both the True and the False outcomes, compared to only one outcome previously. 61895: Cannot insert probe on do/while statement [statement coverage] In VectorCAST version 6.4u, probe points are allowed before the while statement in do/ while loop. 62177: Handle __prog__ pointers for Microchip Previously, VectorCAST created invalid test harness code for some Microchip source code containing __prog__ pointers, causing a compile error. This problem has been resolved in VectorCAST version 6.4u. 62743: Incorrect float values printed in Execution Report when using VCAST_NO_SPRINTF define In recent versions of VectorCAST, floating point values would be incorrectly printed by the unit test harness when using the defined variable VCAST_NO_SPRINTF. This
problem is fixed in VectorCAST version 6.4u. Existing environments should be updated or rebuilt to use the fix. 63008: Stubbed constructor member initialization list should better utilize pointer and reference parameters When VectorCAST stubs a constructor that requires a member initialization list, it tries to use constructor parameters for initializing the members or base classes. If a member or base class initialization requires an initializer of a type not available among constructor parameters, a new instance of that type is created. VectorCAST version 6.4u now attempts to use parameters that are references or pointers to the required type when generating the initialization list. This change reduces the number of new instances created in the harness. 63300: Instrumentation error in Control and Data Coupling Previously, instrumentation insertion points were being miscalculated when gcc was being used due to gcc adding DOS line endings. This resulted in VectorCAST incorrectly placing Control and Data Coupling instrumentation inside existing comments. VectorCAST version 6.4u now accounts for extra DOS line endings to fix the problem.
VectorCAST/Cover: 61053: Support for auto-insert of c_cover_io.c via right-click menu Previous versions of VectorCAST support a CLICAST command to specify that a unit in a Cover environment should have the c_cover_io.c file appended during instrumentation. Doing so eliminates the need to add the /c_cover_io.c file on the command line when compiling the instrumented sources. In VectorCAST version 6.4u, the user is able to do this in the GUI as well. To specify that a C/C++ unit should have the c_cover_io.c file appended, right-click the unit and choose "Append Cover IO". The unit is immediately re-instrumented. Typically, only one unit per Cover environment is selected in order to avoid redefinition errors during compilation, and it is usually the one with the main() function. clicast -e -u cover append_cover_io True | False
62374: Support IO configuration of auto-include of c_cover_io.c VectorCAST/Cover supports the automatic inclusion of the VectorCAST coverage library file (c_cover_io.c or .cpp) into one or more Cover environment source files using the
clicast command: clicast -e -u cover append_cover_io True
In VectorCAST version 6.4u, users have ability to configure the auto-included coverage library using the standard VectorCAST configuration macros. Any configuration macros beginning with "VCAST_" that you define in the "Defined variables" section of the Options dialog, C/C++ tab, are applied to the coverage library during the next instrumentation of the source files in the Cover environment. For example, to configure the coverage library (c_cover_io.c) for standard output, just add "VCAST_USE_STDOUT" to the "Defined variable" options. In clicast, you would use: clicast -lc option C_DEFINE_LIST VCAST_USE_STDOUT
Then re-instrument the files that have been tagged as "append_cover_io" files, and recompile and re-execute your application. 62636: Crash when choosing Environment menu when option "Instrument for function call coverage" is True Previously, a crash occurred when opening the Environment menu after a Cover environment was closed, and the option "Instrument for Function Call coverage" was True. This issue has been fixed in VectorCAST version 6.4u.
VectorCAST/Manage: 39195: Improved preservation of CBA data across source code changes Previously, when C/C++ unit test environments were rebuilt after source code changes, Covered By Analysis data (CBA) was unpredictably discarded, or worse, re-applied on a different line. In VectorCAST version 6.4u, CBA is preserved across source code changes in a predictable manner. During environment Full build/execute, VectorCAST exports the CBA data to a . cvr script with 2 lines of context before and/or after the line with CBA. If any of these lines have changed in the source code, the CBA is discarded and noted in the Coverage Import/ Export Log. Limitations: - the CBA is not retained on Incremental Rebuild for Monitored environments - the CBA is not retained on build/execute for System Test environments - Coverage Import/Export Log is not displayed after environment rebuild. To access this log:
- Open the environment from within Manage and choose Coverage => View Import Log - Open the file IMPORT.LOG in the environment directory 41049: Test case changes lost in VC/Manage Previously, when an environment was updated in one particular context and then another context of the same environment was subsequently opened and then closed, the changes made in the first environment would be lost. Now in VectorCAST version 6.4u, the user is notified that the environment is now out of date because of the previous change and must be updated, rebuilt, or re-executed before it can be opened. 61233: Create, import environment, and migrate in single invocation VectorCAST version 6.4u adds additional functionality to the manage CLI "--import" command. The --import command can be passed the --migrate option from the command line. This will import and migrate an environment to the given group within the given testsuite. 45850: Manage support for continually re-importing Migrated environments VectorCAST version 6.4u includes improved functionality for working with migrated environments. For users who maintain regression scripts or the original environments over source code changes, VectorCAST makes it easy to continually re-import these updated regression scripts or built environments, thus updating the Manage project with the most current version of the environments. A new Manage command, "--re-import", allows the user to re-import existing migrated environments from their initial location from which they were originally imported. The command always uses the same mode of import (.env | ENV directory | regression scripts).
After re-import, CBT can be used to re-run only the tests needing execution based on the changes detected. Note: - Monitored environments are skipped - Cover environments are skipped 62151: Manage build.log shows incorrect sequence of commands and output On Windows, when an incremental build/execute was performed and if the incremental rebuild failed, and a full rebuild followed, Manage was writing to the same build.log for
both commands. In VectorCAST version 6.4u, a separate build.log is produced for each command.
VectorCAST/QA: 58404: Lua Example on Windows Build/Execute failure Previously, the Lua Example located in Examples/SystemTesting/LuaExample had failing test cases when created, built, and executed without making any user changes. In VectorCAST version 6.4u, all test cases pass when executed.
VectorCAST/RGW 62575: RGW Cache file location The Requirements Gateway (RGW) cache file is used to speed up operations that involve multiple updates to the RGW Repository, such as a single test run on an environment with hundreds of test cases. The updates are written to the cache file first, and then once the operation is complete, the cache was committed to another location. In previous versions of VectorCAST, the cache file was written to the Repository directory. VectorCAST version 6.4u changes the location for the cache file to the environment directory to better support multiple users of the same RGW Repository in future VectorCAST releases.
VectorCAST/RSP: 57500: Elements of volatile array in memory region not supported by harness Elements of a volatile array in a memory region, such as the Keil huge region, were not supported in the test harness starting with VectorCAST version 6.3h. Setting an expected value for those elements would result in the text "Not Supported: Cannot_Process" appearing in the Execution report. This problem has been resolved in VectorCAST version 6.4u. 62716: Default VCAST_NO_SETJMP value should be true for the Microchip MPLAB C30 compiler Previously, the default value for the VCAST_NO_SETJMP configuration option was False for the Microchip MPLAB C30 compiler. The False value caused the link error "undefined reference to 'setjmp'" when the source code contained unions. In VectorCAST version 6.4u, the default value is set to True.
62863: Lauterbach TERMGATE integration problems with Hightec tricore-gcc compiler In VectorCAST version 6.4u, the VectorCAST test harness has been updated to correctly support the combination of TERMGATE and the Tricore compiler, where the fpos_t type does not convert automatically to int/long.
Release Notes - VectorCAST: 6.4t VectorCAST C,C++, Ada (Core) 59000: Improved Test Compile functionality for Parameter and Testcase User Code VectorCAST version 6.4t includes improved test compile functionality. In the Parameter User Code and Testcase User code windows, if there a compile error, a new button is displayed. This button opens an editor window containing the temporary preprocessed file that is used to test compile the user code, scrolled to the text in the user code. Using this output may help to debug any user code compile errors. 59421: Support for File Scope Probe Points VectorCAST/C++ and VectorCAST/Cover version 6.4t now support adding a Probe Point at file scope. To add a File Scope Probe Point, first instrument the unit or environment for coverage. Open the Probe Point Editor for the unit. Above the familiar editor for the function scope Probe Points, you see the new File Scope Probe Point. Here you can enter any code that is valid at the file scope, such as new function definitions or global variables. Only one File Scope Probe Point can be entered per unit. Click one of the Test Compile buttons to test compile all active Probe Points (File Scope and regular function scope). When you save and apply the Probe Points for the unit, the File Scope Probe Point is inserted in the instrumented source file just after the last #include line. File Scope Probe Points are written to the regression scripts along with the regular function scope Probe Points. 60127: Crash importing some test scripts specifying attributes Previously, in certain situations, a test script with test cases that contain TEST. ATTRIBUTE lines for elements within an array or structure could cause a testcase
database corruption causing VectorCAST to crash during the test script import. This problem has been resolved in VectorCAST version 6.4t. 61859: Specialized automatic initialization/finalization tests don't execute properly Previously, using auto-initialization/finalization with a specialized test case caused an error dialog during test execution. "VectorCAST was unable to perform the action: CLICAST - RUN_TEST_CASE - TYPES.COMPOUND_DATA_LIST. ACCESSS_RANGE_ERROR". This error has been fixed in VectorCAST version 6.4t. 61914: Tests ignored due to "Ignore incomplete auto-generated test cases" still counted in reports Previously, when generating automatic test cases, if the VCAST_IGNORE_INCOMPLETE_TESTS options was on, and partial/template cases were generated, then even though the script import process would properly ignore the appropriate testcases, the Testcase Management Report would still count them as part of the summary status. This problem has been fixed in VectorCAST version 6.4t. 61964: Jobs window shows elapsed time for Monitored processes Currently, VectorCAST's Jobs window displays the elapsed time for processes called directly by VectorCAST. Previously, VectorCAST could not display the elapsed time for monitored processes. Monitored processes are those that are called by a process that VectorCAST called. An example of a monitored job is when an option is set to call a python or shell script to perform processing. VectorCAST version 6.4t displays the elapsed time of monitored jobs with a duration greater then one second in the Jobs window.
VectorCAST/Ada: 60812: Unable to instrument unit that instantiates from an instantiation Previously, when the UUT was an instantiation of a generic defined in another instantiation, VectorCAST was unable to find the body of the UUT, causing errors during Basis Path calculation and coverage instrumentation. This has been resolved in VectorCAST version 6.4t. 60822: 'pragma inline' in subprogram body gives compile error with SBF Previously, the VectorCAST Ada environment builder would have a compile error when building an SBF environment if a subprogram body in a Unit Under Test contained a pragma INLINE. This problem has been fixed in VectorCAST version 6.4t.
61026: Incorrect handling of INTERFACES.INTEGER_64 type When building range data for standard Ada packages in a Multi-unit Whitebox environment, integer-based numbers do not get range values (by design). Previously, VectorCAST would use the range of 'integer' for test script data verification, which would cause numbers outside of the 'integer' range to be flagged as an error during test script import. In VectorCAST version 6.4t, these numbers are no longer validated at all, allowing the user to enter whatever values are necessary. 61108: Harness build errors with whitebox of nested packages Previously, when building an environment for a UUT with one or more nested packages, the environment builder could fail to correctly implement the type handling procedures used for types within the nested packages. This has been resolved in VectorCAST version 6.4t. 62005: Typemark appearing after nested package body causes compile errors When VectorCAST builds type-handling procedures for a nested package in the UUT, it will build the procedure for all visible types. Previously, that would include all types defined in the enclosing package. When a typemark is defined after a nested package body, this processing would cause compilation errors because the typemark was not defined before the procedure. This issue has been resolved in VectorCAST version 6.4t.
VectorCAST/Analytics: 60423: Support for Importing Custom Analytics Dashboards VectorCAST version 6.4t implements support for saving a Dashboard, modifying it or creating your own, and then importing your custom Dashboard. With a Dashboard open, choose the "Save" icon in the upper right to export the current Dashboard to a JSON file. By default, it is named local_dashboard.vdash. You can then edit this Dashboard file to suit your needs. It is recommended you run it through a JSON validator. When ready to import your custom Dashboard, select the "File Open" icon to import the local_dashboard.vdash file. It is then listed in the dropdown selector as "Local Dashboard Settings." Once you have a Dashboard you like, you can then set it up to be used by everyone connected to the Analytics server by installing it on the machine with the Analytics server. You can install more than one custom Dashboard.
To do this, copy the local_dashboard.vdash file to the Analytics configuration directory and start the Analytics server with the configuration directory: vcdash --project= --config=
If you do not currently use a configuration directory, create one using: vcdash --create-config=vcdash_config
62395: Instrumenting Cover environment in-place prevents Analytics from displaying files Previously, the Analytics Dashboard was not correctly displaying files in Cover environments that were instrumented in-place. To view the source file in the Analytics Dashboard, click the small "file icon" next to the filename in the Project Tree. This problem is fixed in VectorCAST version 6.4t.
VectorCAST/C++: 46821: Parser should accept unnamed parameters for Borland C code Previously, building a C unit test environment that contained unnamed parameters for Borland C code would generate a parser error. This problem has been fixed in VectorCAST version 6.4t. 57345: Invalid stub code generated when return type uses decltype parameter references Previously, VectorCAST generated stub code that did not compile when the return type of a stub used a decltype referring to parameters of the function. This problem has been resolved in VectorCAST version 6.4t. 58160: New gcc/g++ templates for newer versions Default options for gcc/g++ versions 5.2, 5.3, 5.4, 6.0, 6.1, 6.2, and 6.3 are now available in VectorCAST version 6.4t. The following templates have been added to clicast: GNU_C_52 GNU_C_53
GNU_C_54 GNU_C_60 GNU_C_61 GNU_C_62 GNU_C_63 GNU_CPP_52 GNU_CPP_53 GNU_CPP_54 GNU_CPP_60 GNU_CPP_61 GNU_CPP_62 GNU_CPP_63 GNU_CPP11_52 GNU_CPP11_53 GNU_CPP11_54 GNU_CPP11_60 GNU_CPP11_61 GNU_CPP11_62 GNU_CPP11_63 GNU_CPP14_52 GNU_CPP14_53 GNU_CPP14_54 GNU_CPP14_60 GNU_CPP14_61 GNU_CPP14_62 GNU_CPP14_63 60498: Probe Points now available for all statements when using Block Statement Coverage Previously, when "Instrument blocks for statement coverage" was selected, probe points could not be added for statements prior to the last statement of the block. This problem has been resolved in VectorCAST version 6.4t. To get the new behavior, you must reinstrument for code coverage. 61505: Parser using Code Composer flags requires declaration or statement after #pragma DATA_ALIGN In previous versions of VectorCAST, a parse error could occur if #pragma DATA_ALIGN was used in a Code Composer C source file and the #pragma was not immediately followed by a declaration or statement. This problem is fixed in VectorCAST version 6.4t.
61897: Post-preprocess command result not always used In previous versions of VectorCAST, output from a post-preprocessing command might not be used when VectorCAST verified a UUT is parseable in the environment wizard or in the Test Settings dialog (accessed from the Options dialog, C/C++ tab, Test Settings button). This problem has been fixed in VectorCAST version 6.4t.
VectorCAST/Cover: 40767: Control and Data Coupling Verification VectorCAST version 6.4t includes a new implementation of Control and Data Coupling for C/C++ source files in Cover environments for licensed customers. The former implementation in Manage has been removed. This new implementation supports coupling requirements of both DO-178B and DO-178C projects using a combination of static analysis to identify the couples in a code base and run-time verification of the couples during application execution. The intent of the coupling analysis is to prove that the control and data flow between architectural components in the implementation match what was intended by the design, and to prove that these flows have been tested. DO-178B requires applicants to identify couples in the design, and to verify that those couples, and only those couples, exist in the implementation. DO-178C additionally requires applicants to verify that the couples have been exercised during functional requirement testing. DO-178C requires proof that a data object is set before it is used, and that every call of a Control Couple has been executed and that the next statement executed after the call, is the first statement of the called function. VectorCAST's Component Report, Couples Report, and Coupling Coverage Report provide this proof. The feature requires that the sources in the Cover environment be instrumented for coverage. If the sources are not instrumented, the Coupling analysis instruments them for coupling-only coverage. The following coverage types allow coupling: - Statement - Coupling-only (new) The feature requires that all sources listed in the components.xml file (see below) be present in the Cover environment. Therefore, if the user's base directory contains more sources than are planned to be in the Cover environment, the user should edit the components.xml file to only include the sources in the Cover environment. The following is a quick summary of the CLICAST coupling commands:
1. Create Cover environment, add sources. This example uses the name "COVER" for the Cover environment. 2. (optional) clicast -e COVER cover inst STATEMENT | COUPLING 3. clicast -e COVER coupling components 4. Edit COVER/coupling/components.xml if needed 5. clicast -e COVER coupling analyze [] 6. clicast -e COVER coupling apply 7. compile COVER/c_cover_io.c (or .cpp) COVER/ coupling/couplingData.c -ICOVER -I
8. Execute the instrumented application 9. clicast -e COVER cover result add TESTINSS.DAT 10. clicast -e COVER coupling report coverage More information is provided in the VectorCAST/Cover User's Guide. 60844: 'vcast_unit_list_values' now defined as const in vcast_c_options.h When using buffered coverage I/O with VectorCAST/Cover, a global variable vcast_unit_list_values is defined in the c_cover_io.c(pp) file. In VectorCAST version 6.4t, this variable is declared const. In addition, when compiling this file, if a macro named VCAST_UNIT_LIST_VALUES_ATTR is defined, it will be used as part of the variable definition. This allows users to specify declaration attributes such as might be used to specify that a variable be placed in ROM. 61022: Instrumenter very slow when TU has many comments Instrumentation of files with many C style comments is now faster in VectorCAST version 6.4t. 61066: VCAST_APPEND_TO_TESTINSS option is not honored when creating cover environment from CLI Previously, there was no mechanism to set the "Append to Testinss" option for a Cover environment from the command line. In VectorCAST version 6.4t, the capability is correctly controlled by the CLICAST command: clicast -lc Option VCAST_APPEND_TO_TESTINSS True | False
and of course when set in the Options dialog, Coverage tab, Cover Environment sub-tab. A change in value for this option takes effect upon reinstrumentation. 61083: Instrumented file does not compile when "cover append_cover_io" command is used with VCAST_COVERAGE_COLLAPSE_ALL true
Instrumented files did not compile when the clicast cover append_cover_io command was used with a true value and the configuration option VCAST_COVERAGE_COLLAPSE all was set to true. This problem has been resolved in VectorCAST version 6.4t. 61946: Instrumentation speed improvements Coverage instrumentation of some files, especially those using macros, is now faster in VectorCAST version 6.4t. 62024: "Compiler supports long long" option now available on Target tab In VectorCAST version 6.4t, the configuration option "Compiler supports long long" has been moved from the Builder tab to the Target tab.
VectorCAST/Lint: 62053: Lint only environment requires cover license for regression scripts Previously, Lint environment regression scripts would sometimes contain 'clicast cover' commands, which would fail if there were no VectorCAST/Cover license available. In VectorCAST version 6.4t, only 'clicast lint' commands appear in the regression script. 62180: Lint options file environment variable expansion broken from CLI Previously, if the Lint options file used environment variables for paths, the Lint Analysis would only work correctly when called from the VectorCAST GUI. In VectorCAST version 6.4t, environment variables are correctly handled from VectorCAST 'clicast' as well.
VectorCAST/Manage: 33376: Problem in python API reporting of control flow results in Manage Previously, the Python API provided for an environment in Manage would consider an environment having control flow results but no test case expected results as having no results at all. This problem has been fixed in VectorCAST version 6.4t such that the API considers this situation as having results. 53072: Original Source Report incorrect when using Block Statement Coverage The original source report incorrectly labelled some covered lines as uncovered when using the "Instrument blocks for statement coverage" option. Some covered lines were also reported as covered for multiple environments when they were only covered in a
single one. These problems have been resolved in VectorCAST version 6.4t. To get the new behavior in an older Manage project, you must delete the build/ vcast_data/cover.db file from the project directory before reinstrumenting environments for code coverage. 60566: Testcases failing after rebuild in Manage Previously, when a build action was performed on an environment that had execution results, the testcases would be reported as failures because they did not execute as part of the build (only) action. In VectorCAST version 6.4t, the testcase results are removed entirely and reported correctly as NOT EXECUTED. 62208: Manage project wizard crash caused by Refresh action Starting in VectorCAST version 6.4t, the menu options "Refresh" and "Reporting" are not available for environments in the Manage project update wizard.
VectorCAST/QA: 61054: Compile errors after reinstrumenting Linux QA Demo in versions 6.4o and later VectorCAST versions 6.4o and later had compile errors upon reinstrumenting the QA demo on Linux. This problem has been resolved in VectorCAST version 6.4t.
VectorCAST/RGW: 58927: Support for cleaning out historical RGW data from database VectorCAST version 6.4t implements new python scripts to enable the user to manage the size of the Requirements Repository by selectively cleaning out historical Requirements and Test Run data from the database. rgw_report.py and rgw_clean.py, located in the $VECTORCAST_DIR/python/vector/
apps/RGWutility directory, reports on the current historical data in the Requirements database, and clear out all data except the most recent requirements data and test execution data in the database, respectively.
Release Notes - VectorCAST: 6.4s VectorCAST C,C++, Ada (Core) 183: Unused Expected Values capability for User Code VectorCAST version 6.4s implements a new Execute option called "Detect unused expected user code." Enable this option to detect test-specific expected user code that has not been executed during a test. Such code is most likely to be associated with a stub that has not been called. When True and some testcase or parameter user code has not been executed, the test fails, and the Execution Report displays the unused values, the unit, and whether that unit is stubbed or not-stubbed. Disable this option if you have added parameter user code to a stub that you expect to never get called. (You might add code to an uncalled stub if you want the test to show a failure if the stub ever gets called.) clicast -lc|-lada options VCAST_DETECT_UNUSED_EXPECTED_UC TRUE | FALSE
The default value is False. 50748: New Execute option to fail test cases with no Expected Values VectorCAST version 6.4s implements a new Execution option to identify test cases that have no Expected Values. Located on the Options dialog => Execute tab, the option is called "Fail if no expected values." When set to True, a test is prohibited from executing if it does not contain at least 1 Expected Value, Expected Parameter User Code, or Test Case User Code. It is marked as Failed in the Test Case Tree, and appears as "Abnormal Termination - No expected values" in the Testcase Management Report. clicast -lc | -lada option VCAST_TESTCASE_FAIL_ON_NO_EXPECTED True | False
The default value is False. 51686: Informational messages (I) still displayed in Test Script Log with "Only show errors in script logs" set to True Previously, setting the configuration option VCAST_SCRIPT_LOG_SHOW_ONLY_ERRORS to true left informational messages, the ones prefaced by (I), in the test script log. In VectorCAST version 6.4s, the informational messages are removed from the test script log if
VCAST_SCRIPT_LOG_SHOW_ONLY_ERRORS is true. 57031: HTML tag in TXT report when "Generate execution reports in all formats" not checked Previously, VectorCAST added spurious HTML tags to the Execution report in TEXT format when tests were executed while the format was set to HTML, but then changed to TEXT prior to generating the report. The opposite was also true. These problems have been fixed in VectorCAST version 6.4s. The generated Execution or Full report notifies the user that the tests should be executed before re-generating the report in the desired format. Note that setting the option "Generate execution reports in all formats" prior to executing tests eliminates this problem. 57523: Generic Analysis Tool VectorCAST version 6.4s supports a user-configurable static analysis tool, implemented as a Custom Tool. The concept of this new feature is to allow users to run any program that performs file-based source code analysis and view the results of that analysis within VectorCAST's Generic Analysis Viewer. To access the new Custom Tool, choose Static Analysis => Edit Analysis Tools, which brings up a dialog similar to the Custom Tools dialog. To configure a new analysis tool, simply configure the command to be used to perform the analysis, and then ensure that the analysis output is an XML file, formatted in the way that the VectorCAST Generic Analysis Viewer expects. To help you understand how to configure a new Custom Tool, VectorCAST includes a built-in example for use with C/C++ source files. In the Edit Analysis Tools dialog, there is an item called Example Analysis. This item is pre-configured to use VectorCAST/Lint to perform analysis and display the messages using the Generic Analysis Viewer. It uses a python script to invoke VectorCAST/Lint on the source files, and then massages the output into the expected format for the Generic Analysis Viewer. This python file can be used as a template for adding your own analysis tools to VectorCAST. You can use this example as-is by simply checking the box to add the command to the toolbar or menu. Then you can right-click on a C/C++ source file in the open Unit Test or Cover environment and choose Analyze Source => Example Analysis. In the same way, you can recall the analysis results at any time, using the right-click => View Analysis => Example analysis menu item. 59430: Compound Testcase Editor Improvements
VectorCAST version 6.4s has made improvements in the Compound Test Case Editor. Several areas have been changed to make the tool easier to use. These improvements include: - a way to determine which slots are specialized tests - interlocks to prevent a user from dropping or pasting a Specialized test into a nonspecialized compound test and to prevent a user from inadvertently corrupting the test cases - improved drag and drop with multi-selection and - the ability to now search to find text within a slot 60666: "create regression scripts" overwrites .tst symlink with empty file Previously, if a set of regression scripts were actually Linux "links", certain types of links would not be maintained if the regression scripts were re-created over the old files. This problem has been fixed in VectorCAST version 6.4s.
VectorCAST/Ada: 59839: Invalid coverage lines on Ada statements The Ada instrumenter in VectorCAST version 6.4s has been improved to instrument "accept", "begin", and "loop" statements in a more consistent manner. If you have source code with any of these constructs, you may see an increase in coverage totals. 60110: Incorrect instrumentation on single line subprogram Previously, when a conditional statement contained a function call with a parameter as part of a logical comparison, VectorCAST would not always instrument the logical comparison. For example, return F1 ( A ) * F2 ( F3 ( B ) < 0 );
would not show instrumentation for the "F3(B) < 0". This problem has been fixed in VectorCAST version 6.4s. 60825: Stub Object containing constant pointers in private are causes compilation errors Previously, when a global object had been declared using a type mark with an 'access constant' qualifier, VectorCAST would incorrectly build the call to the procedure that could modify the object, resulting in compilation/link errors. This has been fixed in VectorCAST version 6.4s.
VectorCAST/C++: 43621:Startup files list not cleared when changing compiler configurations Previously, when switching from one compiler template to another in the GUI, the list of startup files retained all entries from the first template. In VectorCAST version 6.4s, only user-created entries are retained. 46927: Switching compiler configurations does not always reset certain options Switching compiler configurations did not reset the following configuration options: C_DEBUG_HELP_FILE C_EXEC_HELP_FILE PRECOMPILE_CMD PRECOMPILE_EXT VCAST_ALT_WB_METHOD VCAST_ASSIGN_WITHOUT_COPY_CTOR VCAST_AUTO_CLEAR_TEST_USER_CODE VCAST_DUMP_BUFFER VCAST_FILE_PREFIX VCAST_FORCE_ELAB_TYPE_SPEC VCAST_GH_INTEX_CMD VCAST_GH_INT_FILE VCAST_NO_FFLUSH VCAST_PREPROCESS_PREINCLUDE VCAST_REMOVE_PREPROCESSOR_COMMENTS VCAST_USE_STATIC_MEMORY This problem has been resolved in VectorCAST version 6.4s. 51385: Support GNU type __float128 Previously, VectorCAST did not recognize the GNU types __float128 and __float80. This problem has been resolved in VectorCAST version 6.4s. 57677: Adding configure stubs user code or object initialization user code triggers reinitialization of code coverage Previously, coverage instrumentation was re-initialized when configure stubs user code or object initialization user code was changed. In VectorCAST version 6.4s, the instrumented harness is still linked, but coverage instrumentation is not re-initialized. 59113: Copy VectorCAST tries to create an array initializer with 2 billion elements
In previous versions of VectorCAST, the C++ environment builder would attempt to stub arrays with uninstantiated template-dependent size, leading to a crash. This problem is fixed in VectorCAST version 6.4s. 59303: Error "excessive recursion at instantiation of function" incorrectly given in some cases VectorCAST incorrectly gave the error "excessive recursion at instantiation of function" in some cases where there are many instantiations. This problem has been resolved in VectorCAST version 6.4s. 59793: "Choose a subclass" menu doesn't show all eligible subclasses VectorCAST version 6.4p has a problem where some subclasses were not detected, making them unavailable when setting a pointer of the parent class. This problem has been resolved in VectorCAST version 6.s. If you have an environment built with 6.4p or later with the problem, you must rebuild the environment to get the fixed behavior. 60282: VCAST_DISABLE_STD_CONTAINER_DETECTION should default to FALSE for all compiler templates VectorCAST version 6.4s sets the default value for VCAST_DISABLE_STD_CONTAINER_DETECTION to False for all C/C++ compiler templates. As a result, regression scripts no longer need to include the option unless it is set to True in the environment. 60536: Probe point context matching is incomplete Previously, when applying probe points, VectorCAST would not always handle the context provided properly. In some situations the context-after would be ignored, which would result in an incorrect insertion point for the probe point. This problem has been fixed in VectorCAST version 6.4s. 61152: MC/DC test report does not show branch for ? operator with constant 1st operand in constructor call of a decl not using new The MC/DC test report did not show a branch for the conditional operator when it had a constant first operand and was located in the constructor call of a declaration not using the new operator. This omission did not affect MC/DC test scripts, but it did mean that subsequent conditions received identification numbers that did not match those in the MC/DC coverage report. The problem has been resolved in VectorCAST version 6.4s.
VectorCAST/Cover: 51447: VCAST_CLEAR_COVERAGE_DATA_ID() does not clear vcast_optimized_mcdc_array_* buffers In previous versions of VectorCAST, using VCAST_CLEAR_COVERAGE_DATA_ID() in the c_cover_io.c did not clear buffers related to optimized MC/DC instrumentation. This problem is fixed in VectorCAST version 6.4s. 58455: Crash when instrumenting re-throw statement with function call coverage enabled Previously, VectorCAST crashed when instrumenting for Statement coverage with function call coverage enabled if the source code contained a throw statement without an expression. This problem has been resolved in VectorCAST version 6.4s. 60151: Import of cover script from Ada unit test environment fails if unit only has 'separate' subprograms Previously, if a Coverage script (.cvr) was generated by a VectorCAST/Ada environment and a Unit Under Test in that environment only had 'separate' subprograms, the Coverage script would not import into a Cover environment correctly, causing missing coverage data. This problem has been fixed in VectorCAST version 6.4s. 60904: Invalid instrumentation for ternary expression within union initialization Branch coverage instrumentation did not compile for some C source files containing a ternary expression in a struct or union initialization when the configuration option VCAST_COVERAGE_FOR_DECLARATIONS was set to true and VCAST_AVOID_COMMA_OPERATOR was set to false. Basis paths analysis and MC/DC tests also omitted the ternary expression. These problems have been resolved in VectorCAST version 6.4s.
VectorCAST/Manage: 48791: Import .env file to Manage project to add Monitored environment In Manage, the user can right-click a Group node in a Manage project and choose Add Existing Environment. Previously, the only choice in this dialog was a built Unit Test environment (.vce) or Cover environment (.vcp). With VectorCAST version 6.4s, the user can now select a single environment script (*.env). The environments added using "Add Existing Environment" are Monitored.
manage -p --import <.env file>
Other ways to use the --import argument: manage -p --import manage -p --import <.vce or .vcp file> manage -p --import <.env file> <.tst file> <.csh or .bat file>
Optional arguments can be given as well: [--level=///] [-g ] [--force]
VectorCAST/QA: 45800: System Testing with a partially instrumented application (coverage by component) VectorCAST version 6.4s provides support for component coverage. Component coverage is used when an entire instrumented image is too large to fit on a target. When component coverage is active, the instrumentation of the application is divided and performed for one component at a time, and the full set of tests is run for each component. Using component coverage reduces the amount of memory required to run tests since only a portion of the application is instrumented at any time. Component coverage is disabled by default. See VectorCAST/Manage User guide for additional details. 61408: Add support for selecting and deselecting all tests in Interactive Execute for System Testing environment In VectorCAST version 6.4s, when performing an interactive execute, the user can rightclick in the Select System Test Cases dialog and choose: - Select All - Deselect All
Release Notes - VectorCAST: 6.4r VectorCAST C,C++, Ada (Core) 46909: CSV map "Row containing column headings" not restored When building a CSV map from the GUI, there is an option to specify the number of rows
to skip at the beginning of the CSV file being read (different than the value specifying the header row). Previously, if this value was greater than the value for the header row, only the rows up to and including the header row would be skipped. This has been fixed in VectorCAST version 6.4r, with the addition of the test script line CSV_SKIPPED_ROWS. 60221: vcastqt.exe will not start on Windows XP VectorCAST version 6.4o did not start on Windows XP. This problem has been solved in VectorCAST version 6.4r.
VectorCAST/Ada: 59504: Compile error when stub has object in private section of nested package Previously, when the specification of a stubbed unit contained a nested package, and that nested package contained an object in the private section, VectorCAST would build harness code to try to access the object, even though it is not visible to the harness code. This resulted in a compiler error about the entity not being visible. This problem has been fixed in VectorCAST version 6.4r. 60616: Lowercase tag "--vcast_do_mcdc" causes problem when instrumenting Ada sources for MC/DC VectorCAST searches for special comment tags when instrumenting source code to control instrumentation inside a file. One of these tags, "--vcast_do_mcdc", tells VectorCAST to perform MC/DC instrumentation on the statement(s) that follow the tag. Previously, if the tag was created using anything other than all lower case, the instrumenter for Ada sources would only partially implement the processing, causing instrumentation errors. This problem has been fixed in VectorCAST version 6.4r. 60824: 'pragma elaborate_body' with argument causes harness compilation error Previously, if a UUT specified the "Elaborate_Body" pragma using a parameter (e.g. "pragma Elaborate_Body (UUT);", then VectorCAST would fail to correctly determine the end of the pragma source line and incorrectly generate the harness code for whitebox processing, causing a compilation error. This problem has been resolved in VectorCAST version 6.4r.
VectorCAST/Analytics:
60630: Workflow improvements for Analytics server and history VectorCAST version 6.4r implements improvements to the workflow when working with historic trends in Analytics. The history keeps track of metrics values over time. Typically, a new snapshot is saved at the end of every build/test cycle. To save a history snaphot, enter: vcdash -p --history-dir= --save-history
When you have an existing history directory, invoke the Analytics Dashboard to view data trends: vcdash --history-dir=
In VectorCAST version 6.4r, clicking the "reload" button in the Dashboard loads the newest snapshot. In addition, the Dashboard reloads data when: - a new history snapshot is saved - a history snapshot is removed - a history snapshot is edited To archive the source files used in the Manage project along with the snapshot, enter: vcdash -p --history-dir= --save-history --source-archive
A good practice is to save the source-archive whenever you save a history snapshot.
VectorCAST/C++: 52226: Parse error triggered by inline namespace and noexcept specifiers Previously, VectorCAST gave a parse error for redeclarations of a function template with a dependent exception specification containing an unqualified call to an unknown function if a candidate for that function was introduced in an unnamed namespace following the initial declaration. For example: namespace N { template void f(T p) noexcept(noexcept(f(p))); namespace { void f(); } template void f(T p) noexcept(noexcept(f(p))); // Previously triggered a spurious redeclaration error. Now okay. }
This problem has been resolved in VectorCAST version 6.4r.
57660: Harness incorrectly reuses class instance pointers across units even when class has static linkage In previous versions of VectorCAST, the harness would incorrectly reuse a single class pointer for different classes when the classes had static linkage in different units. This problem is fixed in VectorCAST version 6.4r. 59068: Instrumentation error with probe point in declarative region in C Previously, when the user inserted a Probe Point after a source code line in the C declarative region (such as 'int c = 0;'), VectorCAST would insert the Probe Point in the incorrect location in the instrumented source file. This problem has been fixed in VectorCAST version 6.4r. 59105: Missing break in case produces disputable branch coverage A new Coverage option, "Consider case fallthrough for branch coverage," has been added in VectorCAST version 6.4r. Setting this option to True causes a case statement reached by fallthrough to be treated as a covered branch. Previous versions of VectorCAST behaved as if the option were set to True. In VectorCAST version 6.4r and later, the default value of the option is False. Therefore, coverage reports may differ in this release of VectorCAST. For example, consider the following source code: switch(foo){ case FIRST: i++; case SECOND: j++; }
Branch Coverage: If the option is true, as in previous versions of VectorCAST, then when foo is FIRST, both case FIRST and case SECOND are covered branches. If the option is false, then only case FIRST is a covered branch. Basis Paths: With the example above, if foo is FIRST, previous versions of VectorCAST would show zero covered basis paths. With the option set to False, basis path coverage now recognizes paths that include the fallthrough, so VectorCAST shows one covered path.
Command Line Syntax: clicast -lc option CASE_FALLTHROUGH_BRANCH_COVERAGE True | False
The default value is False. 59465: Parse error "alias template ... may not be used in the type-id of the aliasdeclaration" incorrectly given in some cases The point of declaration of an alias template was changed by C++ standard core issue 1044 to be following the type-id in the alias (i.e., at the point of the semicolon in the declaration). That syntax is now accepted by VectorCAST version 6.4r. Previously, VectorCAST failed to parse the source file, giving the error "alias template ... may not be used in the type-id of the alias-declaration." class A {}; namespace N { template class B {}; template using A = B; // previously gave error }
59910: Unit test harness files in C environments should avoid using C++ style comments Unit test harness files for C environments used some C++ style comments, which caused problems for compilers which did not accept them. For example, the B0000007.c file contained the line if (vcLen == 0) // EOF
Those comments have been converted to C style comments in VectorCAST version 6.4r. 59922: Calls from in-line function defined in header to assembly functions are shown as control couples A new Coverage option, "Asm functions behave as inlines," has been added in VectorCAST version 6.4r for use with Control and Data Coupling. When the option is True, VectorCAST tells the compiler to treat asm functions like inline functions so it can skip over them when adding defined functions to the coupling information. The option is True for DIAB and Green Hills compilers and otherwise False. clicast -lc option ASM_FUNCS_BEHAVE_AS_INLINES TRUE | FALSE
The default value is FALSE except for DIAB and Green Hills compilers. 60287: Probe Point-only instrumentation has problems with declarative regions in C
Previously, when using Probe Point-only instrumentation, using source code with declarative statements, such as shown below: int ccc = 33; { int dd = 44; ccc += dd; }
VectorCAST displayed incorrect subprogram and expression numbers in the Coverage Viewer. This problem has been fixed in VectorCAST version 6.4r. 60291: Allow probe point before declarative region in C VectorCAST version 6.4r now allows the user to insert a Probe Point before a source code line that defines and assigns a variable (such as 'int c = 0;').
VectorCAST/Cover: 60016: Save TU file in cover environment if parse error Previously, the translation unit for a source file was deleted if a parse error occurred. In VectorCAST version 6.4r, the translation unit is now preserved in the cover environment. The name of the file is .tu..preproc. 60428: Coverage viewer shows some covered lines as blank Previously, VectorCAST was incorrectly using "Coverage Field Width" option, which caused covered branch lines to be displayed as blank in the Coverage Viewer when the Coverage Field Width was set higher than the default value. This issue has been fixed in VectorCAST version 6.4r. 60805: Coverage instrumentation inserted outside function for C file with a designated initializer list where a string literal is first Previously, Cover environments for C files containing a designated initializer list where a string literal is the first initializer and the configuration option VCAST_COVERAGE_FOR_DECLARATIONS true, did not compile due to some coverage instrumentation being placed outside of the function being instrumented. This problem has been resolved in VectorCAST version 6.4r.
VectorCAST/Manage:
53765: Manage support for CBA and Imported Coverage in Migrated environments Previously, VectorCAST/Manage did not retain Imported or CBA coverage data when rebuilding migrated environments. In VectorCAST version 6.4r, both Imported Coverage and Coverage by Analysis data are exported to a coverage script (.cvr) and reimported after the environment is done building. With this improvement to VectorCAST, you will see the following changes: - In the Diff dialog that appears when closing a Migrated environment in Manage, two new tabs are displayed. One is for CBA results and the other is for Imported coverage results. It is recommended that these coverage scripts (.cvr files) be kept under source code management. - If a Monitored environment that originally contained CBA or Imported coverage is migrated, the coverage data is now retained upon building, and therefore appears in the Project Tree and the various Coverage reports. 59773: "Cannot open the environment" error in Manage Previously, when a build error occurred during Incremental Rebuild, Manage was incorrectly showing that the environment could still be opened but then prohibited it from opening. In VectorCAST version 6.4r, an environment is openable in Manage if it is openable outside of Manage, that is, in VectorCAST/C++ or VectorCAST/Ada.
VectorCAST/RGW: 57467: [MDS Technology] Popup error from integration with PTC integrity Previously, the PTC Integrity Integration was not correctly importing Requirements containing non-ASCII codepoint UTF-8 (e.g. Hangul, Hanzi, Hiragana, etc.). Such characters were being incorrectly imported as '?'. This problem has been fixed in VectorCAST version 6.4r. 58870: Requirements Gateway in SQLite mode, by default VectorCAST version 6.4r fully implements the Requirements repository in SQLite mode. This means that when creating a new repository in CLICAST or in the GUI Requirements Gateway dialog, the new SQLite mode is used. See the VectorCAST/C++ or VectorCAST/ Ada User's Guides for more information, in sections "Using VectorCAST/Requirements Gateway" and "Appendix H: RGW - Command Line Reference."
If a Legacy repository exists and the user does not migrate to the new SQLite mode, it remains in Legacy mode. To migrate a Legacy repository to the new SQLite mode, follow these steps: 1. Open any environment that uses the Requirements repository and export any pending testcase pass/fail data back to the 3rd-party Requirements tool. 2. Exit the GUI. 3. Initialize the new repository: "clicast -lc|-lada RGw Initialize" 4. For each environment that uses the repository, the associations between testcases and requirements must also be migrated. To do this, choose one method: a. Execute all tests (in each environment) b. Run "clicast -e RGw Testcase Migrate_links" (on each environment) c. If the environments are in a Manage project, use: "manage -p [--level=] --clicast-args RGw Testcase Migrate_Links"
VectorCAST/RSP: 60512: Global defined '@ address' should not be declared 'extern' in VectorCASTgenerated object interface file Previously, the VectorCAST test harness for IAR code containing variables defined '@ address', declared those variables extern when Object File testing was selected. The added extern keyword caused link errors. This problem has been resolved in VectorCAST version 6.4r.
Release Notes - VectorCAST: 6.4q VectorCAST C,C++, Ada (Core) 55844: Incorrect status in the Execution Status window after harness crashes Previously, the Execution Status window would show the status of a test's execution based in part on the harness' execution status and in part on the test's pass/fail status. When the Execution Status window indicated a test passed but the Test Case Tree showed it failed or terminated abnormally, the discrepancy could be confusing. With VectorCAST version
6.4q, the two sources of information have been synced so the status is the same in both places. 57595:Test case derived from MIN/MID/MAX generates error message when range data not calculated Previously, if a test script had test cases derived from the MIN/MID/MAX test case, and the script was imported into an environment where Range Checking is set to None, the command-line would crash when executing one of those test cases, or the GUI would display a non-helpful error message. Starting with VectorCAST version 6.4q, test script import now identifies this situation as a failure condition, thus preventing a command-line crash or GUI error message on execution.
VectorCAST/C++ and VectorCAST/Cover: 52911: Allow "sprintf" for probes Previous versions of VectorCAST provides Probe Point users with a replacement function for printf named "vcast_probe_print." This function, when included in a Probe Point that was reached during test execution, would print out the string argument to the stdout (for Unit Test environments) or to the TESTINSS.DAT file (for Cover environments). However, this function did not provide users with a way to output the values of integer variables, unsigned int variables, or floating point variables. VectorCAST version 6.4q provides functions enabling users to print variables of all of these data types to stdout (or TESTINSS.DAT): - string: use vcast_probe_print - int: use vcast_probe_print_int - unsigned int: use vcast_probe_unsigned - float: use vcast_probe_float To get the new Probe Point functions: - VectorCAST/Cover users must create a new Cover environment - VectorCAST/C++ users must rebuild existing unit test environments or create a new one.
VectorCAST/Ada: 58224: Improve parameter tree indications of objects that cannot be set/inspected
In certain situations, the VectorCAST parameter tree would allow the user to set Input or Expected Values for certain parameters or objects that the harness could not actually modify/inspect (for example, a pointer to an unconstrained array), causing the following error message to appear when generating the Execution Report: *Not Supported: Cannot_Process*
In VectorCAST version 6.4q, these parameters now show their type as 'user' in the Parameter Tree, and the tooltip for the typemark indicates the reason that User Code is required to set/inspect the parameter. 59165: Some subtypes of enumerated type gets incorrect range for certain targets Because of the limitations of certain targets, in some cases the VectorCAST harness uses "case" statements and "for" loops to set/print enumerated types. Previously, in these situations, if an enumerated subtype did not start with the first enumeral in the base type, then the enumerals displayed in the Parameter Tree and Execution Report were incorrect. This problem has been fixed in VectorCAST version 6.4q.
VectorCAST/C++: 42498: Constructor call not imported from test script when constructor name contains '[' character Attempting to import test scripts where a constructor name in a constructor call contained the '[' character resulted in VectorCAST giving the "Value Line Error Command Ignored" error message. The data on the line was lost during test script import. This problem has been resolved in VectorCAST version 6.4q. 56867: Probe Apply seems to instrument all files In previous versions of VectorCAST, adding, removing, or modifying probe points would trigger the instrumentation of all files when applying. Only the ones modified need to be reinstrumented. This problem has been fixed in VectorCAST version 6.4q. 57159: New option "Parse function templates" A new C/C++ option, "Parse function templates", is available in VectorCAST version 6.4q to control parsing of function templates. VectorCAST parses templates in a generic way in order to instrument templates for code coverage. This generic processing is more likely to trigger parse problems because the information provided by specific instantiations is not available, and because compilers sometimes allow errors if a template is not instantiated. The new option, located in the Options dialog, C/C++ tab, Language sub-tab, controls
whether VectorCAST parses function templates in this generic way, which is useful when a template parse problem is encountered and the source code cannot be changed. Disabling the option can allow the parsing to succeed in such cases, but will prevent code coverage instrumentation of function templates. clicast -lc option VCAST_PARSE_FUNCTION_TEMPLATES TRUE | FALSE
The default value is True. 57477: ASCII output buffer coverage option does not compile in 64m and later versions for unit test Environments built with VectorCAST versions 6.4m or later did not compile if the configuration option VCAST_USE_BUFFERED_ASCII_DATA was set to TRUE and coverage was initialized. This problem has been resolved in VectorCAST version 6.4q. 58182: Include unit prefix/appendix user code in macro detection VectorCAST detects macros so that they can be used when specifying input or expected values in the test case parameter tree without using user code. In previous versions of VectorCAST, this detection did not include macros that came from unit prefix or unit appendix user code, or files #included from those. This problem is fixed in VectorCAST version 6.4q. 58781: VCAST_DUMP_COVERAGE_AT_EXIT should be ignored in unit test environments VCAST_REGISTER_DUMP_AT_EXIT() calls to each instrumented function in a Unit Test
environment when Buffered coverage was used and the configuration option VCAST_DUMP_COVERAGE_AT_EXIT was set to true. Those function calls were not necessary for unit test environments. In VectorCAST version 6.4q, the VCAST_DUMP_COVERAGE_AT_EXIT configuration option has no effect on Unit Test environments. The configuration option is still used for cover environments. 59370: Parse error using template template parameter as template template argument VectorCAST incorrectly gave a parse error when some source code contained a variadic "template template" parameter of one template that was passed as a template template argument to another template. For example, template class> struct A; template class TT> struct B { using X = A;
};
could not be parsed. This problem has been resolved in VectorCAST version 6.4q.
VectorCAST/Cover: 44527: Improve c_cover_io.c to simplify use of custom output VectorCAST version 6.4q recognizes two new macros to aid in customizing coverage data output in c_cover_io.c. The new macros are only recognized when the macros VCAST_USE_STDOUT and VCAST_CUSTOM_STD_OUTPUT are also defined. Define VCAST_CUSTOM_STD_OUTPUT_INCLUDE as a path to a separate file that will be #included into the VCAST_WRITE_TO_INST_FILE_COVERAGE function with c_cover_io.c. The separate file would need to contain the code that implements writing coverage data. Define VCAST_CUSTOM_STD_OUTPUT_EXTERNAL to specify the name of a function defined elsewhere to implement writing coverage data. The function must match the prototype: void VCAST_CUSTOM_STD_OUTPUT_EXTERNAL(const char* S, int flush);
47602: help text for VCAST_INSTRUMENT_ASSIGNMENTS should not mention conditional operator Starting with VectorCAST version 6.0a, the configuration option VCAST_INSTRUMENT_ASSIGNMENTS did not affect instrumentation of the ? operator. However, the help text for VCAST_INSTRUMENT_ASSIGNMENTS was not updated. Beginning with VectorCAST version 6.4q, the help text for VCAST_INSTRUMENT_ASSIGNMENTS is now correct. 56660: c_cover_io functions lack prototypes Function prototypes have been added to the c_cover_io files in VectorCAST version 6.4q. This change allows successful compilation of the instrumented source files with the IAR compile option '--require_prototypes' or with the GNU compile options '-Wmissingdeclarations -Werror'.
59075: Regression script referenced Probe Point file in Cover Environment directory, but shouldn't In previous versions of VectorCAST, the generation of a regression script for a Cover environment failed to create a proper probe point file, and so the probe points were not
preserved. This problem has been fixed in VectorCAST version 6.4q.
VectorCAST/Manage: 36930: Manage executes testcases in a monitored Environment even if it failed to rebuild In previous versions of VectorCAST, when a build-execute was initiated on a monitored environment, the environment's test cases would be executed even if the environment rebuild failed. This issue has been resolved in VectorCAST version 6.4q. 58259: Crash with VC/Manage when creating project from existing environments In previous versions of VectorCAST, it was possible for VectorCAST/Manage to crash while factoring the configuration of an environment which has an invalid compiler tag. This issue has been resolved in VectorCAST version 6.4q.
VectorCAST/QA: 58982: 104% in klocwork plugin In previous versions, some static analysis metrics (percent clean functions, number of clean functions) used erroneous function counts, causing percentages to be greater than 100%. These metrics have now been fixed in VectorCAST version 6.4q.
VectorCAST/RSP: 56946: DDCI for Ada RSP VectorCAST version 6.4q implements support for the DDC-I Score DEOS run-time, both for simulated and live-board targets. Use of this Ada RSP requires the licensed feature "VectorCAST/Ada SCORE DEOS" to be available. To use the new RSP, set the option "Target Variant" to "SCORE DEOS" in the Options dialog, Target tab. clicast -lada -x SCORE_DEOS environment build .env
When running VectorCAST for DDCI-Score, the user must start VectorCAST application from within the appropriate DDC-I console to enable access to the entire DDC-I toolset. 58786: IAR parse error and harness compile error for array size using sizeof a field in the same structure
VectorCAST incorrectly gave a parse error for IAR source code containing an array size using a sizeof expression for a field in the same structure. For example, typedef union { struct { int i ; } foo; char array [sizeof(foo)] ; } sample_union;
gave an error that foo was undefined. This problem has been resolved in VectorCAST version 6.4q. 58995: Enumerated typemark in one UUT causes compile error when used in another UUT for certain targets With certain Ada targets, the VectorCAST harness needs to build a "case" statement with all of the enumerals in an enumerated type. If a UUT references an enumerated type in another UUT, this list could have been built incorrectly, causing harness compilation errors. This problem has been resolved in VectorCAST version 6.4q. 59022: Option to control dynamic allocation for pointers on certain targets Previously, for certain Ada targets, the environment builder made assumptions as to whether dynamic memory allocation (such as when using the 'new' operator) was allowed, based solely on the selected target variant option. This determination meant that if the user configured a particular target kernel to change how the dynamic memory allocation worked, there was no way to modify the VectorCAST harness behavior. In VectorCAST version 6.4q, there is a new target option named "No dynamic memory allocation", which enables the user to inform VectorCAST that complete processing for access types is or is not supported, thus overriding the default behavior for that target. clicast -lada option NO_DYNAMIC_ALLOCATION True | False
The default value is set by the specified target.
Release Notes - VectorCAST: 6.4p VectorCAST C, C++, Ada (Core)
37078: 'clicast tools regression_test' scripts should preserve symlinks Previously, on Linux and Solaris, if the tester had regression scripts that were symbolic links and then regenerated the regression scripts from VectorCAST, the symbolic links would be broken and the originally linked files would not be updated. This has been fixed in VectorCAST version 6.4p. 51938: Test Compile for Probe Points available With VectorCAST version 6.4p, a Test Compile feature for Probe Points is available in the Probe Point Editor for VectorCAST/C++ unit test environments and Cover environments. Clicking the Test Compile button located in the right-hand panel of the Probe Points Editor performs a Test Compile of all active Probe Points in the unit. Deactivated Probe Points are not compiled. The Test Compile action preprocesses the unit, inserts the Probe Points into the preprocessed file, and compiles the file. Error output from this action is displayed at the bottom of the Probe Point Editor. Clicking the button with the file icon opens the preprocessed file, enabling the user to diagnose the compile error. 55860: Test scripts created with incorrect file permissions on linux/solaris Previously, when creating test scripts on Linux/Solaris systems, the file permissions for the script would be set to only allow the user Read/Write access (600), instead of whatever the operating system would generate as a default. This has been fixed in VectorCAST version 6.4p. 56199: Save all user-specified options to CFG file when VCAST_LEGACY_CFG_FILE_INHERITANCE is set Recently, VectorCAST changed the behavior of Configuration files (*.CFG) to only read the local *.CFG file, not those found in the installation directory or the user's home directory. For users needing the old behavior, setting the environment variable VCAST_LEGACY_CFG_FILE_INHERITANCE reads the .CFG files from all three locations. The problem with this solution was that the environment variable would always need to be set whenever a regression script was executed. Starting with VectorCAST version 6.4p, if the environment variable VCAST_LEGACY_CFG_FILE_INHERITANCE is set, any options inherited from the installation directory or user's home directory are saved to the local *.CFG file, creating a complete set of options from all sources in one place (the local *.CFG file). Once this is done for each environment, the environment variable no longer needs to be set when running the regression script.
58484: Crash when executing test cases while still saving Control Flow Previously, executing test cases while the process of saving Control Flow or changing an <> test case to Automatic Initialization/Finalization was still processing, could cause a crash. In VectorCAST version 6.4p, a modal progress dialog has been added to the following processes: save control flow, clear control flow, automatic initialization and automatic finalization, to prohibit test execution while the status of the test cases is still processing.
VectorCAST/Ada: 57262: Environments from GPR files not always building correctly in Windows toplevel directory Previously, when an Ada environment was built using a .GPR file, and the .GPR file resided at the top-level of a Windows drive other than 'C', the environment could fail to build due to the inability of VectorCAST to correctly find 'separate' modules of the Unit Under Test. This has been fixed in VectorCAST version 6.4p. 57714: Consecutive labels in Ada source code causes instrumentation error Previously, source code with consecutive Ada labels and optional comments caused VectorCAST instrumentation to fail. <<>> -- Comment <<>> -- Comment <<>>
These problems are fixed in VectorCAST version 6.4p. 57994: Environment build error when Ada function has a precondition Previously, when a function had a pre-condition (or other aspect), VectorCAST would not always parse the return type correctly, resulting in a compilation error. This problem has been fixed in VectorCAST version 6.4p. 58104: Support Unconstrained Arrays in generics Previously, VectorCAST was not able to build Ada environments for Ada generic units containing unconstrained arrays. This problem has been fixed in VectorCAST version 6.4p. 58429: Add support for 'limited' types in Ada stub parameters
Previously, if a stub parameter (or return object) was of a 'limited' type, the user could set an Input or Expected Value in the Parameter Tree, but the value would not be set (or the comparison would fail) because the harness could not copy objects of 'limited' type (due to language restrictions). Starting with VectorCAST version 6.4p, objects of 'limited' types are now manipulated in VectorCAST using a "memory copy" technique, allowing Input and Expected Values to behave correctly. 58580: Harness build error with source code having non-null access procedure as parameter declaration Previously, when building an Ada environment containing parameter declarations that access a procedure or function, VectorCAST generated code that did not compile properly, causing a compile error to appear while compiling the test harness. For example, a source file with the following parameter declarations did not build successfully: procedure UUT_PROCEDURE ( UUT_PARAM1 : in integer; UUT_PROC_PTR : access procedure ( UUT_PARAM2 : in out integer ));
In VectorCAST version 6.4p, the environment builds successfully, but these kinds of parameter declarations are not supported. It is recommended that you modify your code to use an access type as follows: type ACCESS_PROCEDURE is access procedure ( UUT_PARAM2 : in out integer ); procedure UUT_PROCEDURE ( UUT_PARAM1 : in integer; UUT_PROC_PTR : ACCESS_PROCEDURE );
Using this source code, VectorCAST is able to successfully build an environment and the access type is supported. 58898: Enumerated subtypes in UUT can generate invalid Ada code for some targets For certain targets, when a UUT is a child package, objects or parameters in the UUT that were defined using a subtype of an enumerated type could cause the harness to be built incorrectly, which resulted in compilation errors. This problem has been resolved in VectorCAST version 6.4p.
VectorCAST/C++: 55842: GUI not updated after parameter user code reset Previously, the "Reset" action in the Parameter Properties dialog was not properly resetting parameter user code for 'struct' and 'record' data types. The right-click "Clear" menu action was also not clearing the same parameter. This issue has been fixed in VectorCAST version 6.4p. 57235: Parse Error with Visual Studio 2015 C++ when instantiating standard containers Previously, some Visual Studio 2015 code instantiating standard containers caused VectorCAST to give the error: function... (declared implicitly) cannot be referenced -- it is a deleted function.
This problem has been resolved in VectorCAST version 6.4p. 58039: Test harness does not compile when function-level try/catch statements are in stub-by-function units Previously, the test harness did not compile when function-level try/catch statements were in stub-by-function units. The stub-by-function modification was inserted in the middle of the "try" keyword. This problem has been resolved in VectorCAST version 6.4p. 58117: Not able to change "<>" value to no value in the Parameter Tree After removing <>, <> or <> from the input enumeration parameter, the test case was not marked as needed to be saved. Thus, the value could not be successfully cleared. This problem has been corrected in VectorCAST version 6.4p. 58197: Test script error when running script after rebuild Previously, during environment rebuild, VectorCAST's python data API may have become corrupted until the environment was rebuilt a second time, causing an error message that starts with: 'NoneType' object has no attribute 'id'
This problem has been fixed in VectorCAST version 6.4p.
58356: Allow "Suppressed Stubs" to suppress SBF instrumentation VectorCAST version 6.4p now allows the "Suppress Stubs" functionality in the Create New Environment Wizard to suppress stub-by-function instrumentation in the test harness. Stub-by-function instrumentation is seen under the <> node in the Parameter Tree. Previously, this functionality only allowed the suppression of stubs generated when a function body did not exist. In the environment script (.env), use the following command to suppress Stub-byFunction instrumentation for a particular testable function in an SBF unit under test: ENVIRO.STUB_BY_FUNCTION: ENVIRO.SUPPRESS_STUB:
58968: Symbolic constants not detected following #define of certain expressions Source code containing a #define to an expression with a right brace not preceded by a left brace yet followed by a left brace not followed by another right brace caused subsequent #define statements to be missing from the symbolic constants window. This problem has been resolved in VectorCAST version 6.4p. If you have the problem with an environment, you must rebuild the environment to get the new behavior.
VectorCAST/Cover: 51331: Disable code and data definitions for non-optimized MC/DC instrumentation if all statements use optimized MC/DC instrumentation uses different implementation techniques depending on the VectorCAST configuration and the nature of the code being instrumented. In VectorCAST version 6.4p, the functions and data variables used for non-optimized MC/DC instrumentation in c_cover_io.c are disabled when not needed. 57279: Multiple variable declarations in single source statement incorrectly treated as multiple coverable statements Previously, VectorCAST treated multiple variable declarations with initializations in a single source statement as multiple coverable statements. For example, int a=0, b=0;
was considered to be two coverable statements. In VectorCAST version 6.4p that will be treated as a single statement.
58382: Empty preprocessor output causes vc/cover to crash Previously, VectorCAST crashed when instrumenting a source file if the preprocessor output was empty. This problem has been resolved in VectorCAST version 6.4p.
VectorCAST/Manage: 48144: Improved feature for adding an environment to a Manage project Previously, the --import command required that the group be explicitly added to the testsuite on the next command line. In VectorCAST version 6.4p, this is no longer necessary. Therefore, the following command imports the environment to the Manage project given that all nodes exist: manage -p --level -g --import where is: ///
If one or more nodes does not exist, a new --force option can be given, which creates any of the nodes as necessary before importing. manage -p --level -g --import [--force]
51201: New Manage Status window improves environment build and execute usability VectorCAST version 6.4p provides a new window that displays the Build and Execute progress of environments in a Manage project. The Manage Status window is similar to the Execution Status window in Unit Test environments. 57199: Removing one environment in Manage can result in all Envs being removed Previously, the Group node in a Manage project would remain selected after creating a new environment in that group. If the user's next step was to delete an environment in that group, all environments were deleted because the Group node was selected. This workflow has been improved in VectorCAST version 6.4p by leaving only the environment selected after a new environment is created from the Project Tree. 57292: Replace SCM with File Hooks Scripting VectorCAST version 6.4p includes a new option for Manage projects. File hook processing provides an open python interface to interact with the VectorCAST project and migrated environment files that would normally be involved in source code management (SCM). This feature allows the user to perform actions, such as modifying file permissions, line endings, or other processing, before and after VectorCAST modifies them.
The following files for migrated environments are audited by the File Hooks Script: - project.vcm file - project.db file - *.mfg files - *.cfg files - *.env files - *.tst files, including specialized test case scripts To enable the functionality, choose Project => Options, and turn on the option "Enable File Hooks scripting." or enter the following command manage -p --enable-file-hooks-scripting manage -p --disable-file-hooks-scripting
If enabled, the following actions trigger the File Hooks Script to run: - migrating an environment - building and executing an environment - modifying an environment - modifying the project (i.e. adding or removing an environment) - storing results To edit the python script, choose Project => Edit File Hooks Script. When saved, the python file is reloaded. In the case of a compile error, VectorCAST alerts the user of the failure in the Message Window and if the python file is still open in the editor, scrolls to the approximate location of the error. 57350: Incremental rebuild should become full rebuild when env script has changed in Manage environment directory Previously, when performing an incremental build/execute, VectorCAST/Manage did not consider any environment script (.env) file changes as the basis for rebuilding migrated environments. In VectorCAST version 6.4p, changes to the environment script (.env) file cause an environment to be fully rebuilt. 57454: Lock is not being removed when Aborting execution of a monitored environment In previous versions of VectorCAST, aborting the execution of a monitored environment resulted in the environment being left in a locked state. This issue has been resolved in VectorCAST version 6.4p. 57819: Clean does not work when invoked from group level In the GUI, when the Clean menu item was selected from a Group node, the action was
not performed. Also, the Migrate to Workspace menu item was not available from a Group node. In VectorCAST version 6.4p, Clean and Migrate to Workspace can be performed from a Group node successfully.
VectorCAST/RSP: 56970: Blackfin 706 types not supported by parser __builtin_quad _Fract _Accum _Sat In previous versions of VectorCAST, errors would occur when parsing VisualDSP code which used the built-in type __builtin_quad or fixed-point types _Fract and _Accum. This problem is fixed in VectorCAST version 6.4p. 57166: Support Borland feature allowing 'using namespace ...' declaration in class scope Previously, VectorCAST gave an error when reading Borland source code containing "using namespace ..." declarations inside class definitions. This problem has been resolved in VectorCAST version 6.4p.
Release Notes - VectorCAST: 6.4o VectorCAST C, C++, Ada (Core) 51837: MC/DC pairs column in Environment View vanishes after rebuild Previously, following the rebuild of an environment with initialized MC/DC coverage, the MC/DC pairs column in the Test Case Tree remained hidden. This has been fixed in VectorCAST version 6.4o. 52110: Highlight the filterable table widget selections in the test tree in VC/C++ VC/ Ada VectorCAST version 6.4o adds a new highlighting functionality to the Test Case Tree. Items in the Test Case Tree are highlighted with a custom yellow background when a corresponding item is selected in either the Test Data Summary table, the Coverage Summary table or the Job Monitor - Execution Status window. Note: If both the Execution Status window and the Test Data Summary are open, the selection in the Test
Data Summary table has precedence. 57287: Coverage Viewer is unusable when source has many lines and MC/DC Tables are expanded Previously, VectorCAST took a long time to display original source lines in the Coverage Viewer with over 40k lines; expanding all subprograms also took a long time when MC/ DC coverage was initialized. These problems have been corrected in VectorCAST version 6.4o. VectorCAST no longer automatically expands all MC/DC tables when expanding all subprograms in the Coverage Viewer and Coverage-By-Analysis Editor; displaying original source lines no longer decreases performance of the Coverage Viewer. 57355: When opening a new editor, scroll to the line selected in the previous editor Starting in VectorCAST version 6.4o, when opening a new editor, it will automatically scroll to the same line in an open Coverage Viewer, Probe Point Editor, CBA Editor, or Source Code editor if the unit is the same. To turn off the automatic scrolling behavior for any editor, right-click in the editor and select "Map Selection to Original Source View" to uncheck it.
VectorCAST/Ada: 57432: SBF units that are child packages can have compile errors with parent unit types Previously, when building a Multi-unit Whitebox Ada environment for an SBF unit, if the SBF unit was a child unit that referenced a variant record in a parent unit, VectorCAST could build the harness files incorrectly, resulting in a compilation error. This problem has been resolved in VectorCAST version 6.4o. 57575: Support for GNAT 17 With the release of GNAT 17, some of the underlying interfaces of the compiler tools have changed, preventing VectorCAST from building environments from GPR files. This problem has been resolved in VectorCAST version 6.4o. 57649: Uppercase Boolean values changed to lowercase upon reopening testcase Previously, the Boolean parameters TRUE and FALSE were displayed in lowercase after reopening a test case. This issue has been fixed in VectorCAST version 6.4o.
57787:Support Ada Generic Variant Record Previously, VectorCAST was not able to build Ada environments for Ada generic units containing variant records. This problem has been fixed in VectorCAST version 6.4o. 58068: Ada environment builder blocks type handling for pragma pure Previously, when creating a blackbox environment for a 'pure' unit, parameters could be set/inspected in the parameter tree, but the values would not appear in the execution results. This has been fixed in VectorCAST version 6.4o.
VectorCAST/Analytics: 54416: Analytics Quick Launch Button VectorCAST version 6.4o introduces a new Start Analytics button on the main toolbar that allows VectorCAST/C++, VectorCAST/Ada and VectorCAST/QA users to easily launch a VectorCAST/Analytics dashboard for unit test or coverage environments. The VectorCAST/Analytics dashboard provides a web-based dashboard view of software code quality and testing completeness metrics, making it easy to understand the current state of quality and testing completeness for a software project. This critical actionable intelligence allows all stakeholders to make decisions about release readiness and process improvement. To open the Analytics Dashboard, click the Start Analytics button located on the toolbar when an environment is open. Once the Start Analytics button is selected, the Analytics Monitor opens in the MDI window. The Automation Controller within VectorCAST automatically pulls the information from the open environment, adds it to a Manage project in a workarea, and launches the Analytics dashboard in the default browser using localhost:8128. The Automation Controller Output pane, displayed at the top of the Analytics Monitor, shows the output of the Automation Controller scripts and the lower pane shows the Analytics Server Output. To stop the Analytics server, click the Stop Server button at the bottom of the Analytics Monitor window. You can find more information about the Analytics Dashboard and the Analytics Toolbar button in the VectorCAST Quick Start Guide in the chapter entitled "Publish Project Metrics".
VectorCAST/C++: 42650: New optional "Constant branch conditions" section for reports
In VectorCAST version 6.4o, a new option, "Display constant branch conditions in reports", has been added. When enabled, this option adds a new section to the Metrics report that identifies the unit, subprogram, and line number of any branch or MC/DC expressions that have constant values, such as "if (1)". clicast -lc option VCAST_DISPLAY_CONST_BRANCH_CONDITIONS TRUE | FALSE
The default value is FALSE. 56574: Setting attribute for member of container class causes incorrect script generation When using VectorCAST's Test Case Editor to enter data for standard container class objects (maps, pairs), if the user sets an attribute for the parameter (such as numeric base or display flag), the test script generated for that test may contain invalid lines, causing test script import to fail. This problem has been resolved in VectorCAST version 6.4o. 57198: Coverage Viewer shows incomplete coverage when block coverage enabled Previously, VectorCAST would display incomplete coverage in the Coverage Viewer when the option "Instrument blocks for statement coverage" was True. VectorCAST version 6.4o fixes this problem. Unit test and Cover environments built with previous versions of VectorCAST will need to be re-instrumented in order to show the correct coverage in the Coverage Viewer. 57280: Crash during basis path analysis for function which uses anonymous union In previous versions of VectorCAST, basis path analysis could crash VectorCAST if a function's return statement used an unnamed union. This problem is fixed in VectorCAST version 6.4o. 57484: Support '= 0' initialization for arrays in microchip Microchip MPLAB compilers allow arrays to be initialized simply with '= 0'. In previous versions of VectorCAST, the parser would raise an error on such initializations. This problem is fixed in VectorCAST version 6.4o.
VectorCAST/Cover: 49297: Remove unused variable vcast_max_covered_subprograms_exceeded from c_cover_io.c VectorCAST version 6.4o removes an unused variable 'vcast_max_covered_subprograms_exceeded' from c_cover_io.c.
57013: Clicover crash during instrumentation when original source directory is missing Previously, when using CLIcover to perform instrumentation on a Cover project, if the original source directory is no longer available, VectorCAST would crash. This has been resolved in VectorCAST version 6.4o. 57642: Could not delete Cover env because a file VCAST_GUI_SIZES.plist remained in the env dir Previously, a Cover environment could not be fully deleted because a file was left in the environment directory. This has been fixed in VectorCAST version 6.4o. 58030: Infrequent crash instrumenting for Probe Point in Cover env When instrumenting a unit in a Cover environment for Probe Point coverage, VectorCAST version 6.4n could sometimes crash the GUI. This problem has been fixed in VectorCAST version 6.4o.
VectorCAST/Manage: 53373: Not all compiler settings overwritten when duplicating a compiler node and setting to a new compiler Previously the compiler options for a configuration would not be cleared when setting a new compiler template. This issue has been resolved in VectorCAST version 6.4o. 56719: Manage workflow drag and drop for monitored environment VectorCAST version 6.4o has improved drag-and-drop functionality for moving monitored environments within manage. Monitored environments can only exist in one context so they are moved from one location to another. Migrated environments will create a new clone in the new location. If a selected node contains both monitored and migrated environments, all the environments in that node are moved to the new location. 57123: Allow user to retry renaming environment working directory when creating new environment Previously, when creating a new environment in Manage, and the temporary location for creating it could not be renamed due to a process still running in that temporary directory, a vague error message prompt (such as "Error renaming file 1366962433 to 340505613") was displayed and the Create New Environment transaction was cancelled.
VectorCAST/QA: 55618: Need a formal way to handle backward compatiblity when we add new stuff to system_test.py The QA examples, LuaExample and ManagerExample, have been updated in VectorCAST version 6.4o. The examples are created by running the createExample script that corresponds to the operating system (Linux or Windows). Linux: To create the Lua example, run the createLuaExample.sh script located in Examples \SystemTesting\LuaExample\Linux.
To create the Manager example, run the createManagerExample.sh script located in Examples\SystemTesting\ManagerExample\Linux.
Windows: To create the Lua example, run the createLuaExample.bat located in Examples \SystemTesting\LuaExample\Windows. To create the Manager example, run the createManagerExample.bat located in Examples \SystemTesting\ManagerExample\Windows.
VectorCAST/RSP: 57552: Parser for Diab fails to disambiguate scope qualifier that matches enum typedef In previous versions, VectorCAST's parser in Diab mode would fail to disambiguate an identifier used as a scope qualifier when the identifier was also used as an enum typedef name. This problem is fixed in VectorCAST version 6.4o. 57794: Subtypes of enumerals not handled correctly in some Ada target harnesses On certain Ada targets, 'image and 'value are not supported, so processing to set/print enumerated types use "if" and "case" statements with the fully qualified enumeral name. In previous versions of VectorCAST, for a package that used a subtype of an enumerated type in a second package, and the parent type of the enumerated type was in a third package, the test harness code would be generated with the incorrect location of the enumeral. This has been fixed in VectorCAST version 6.4o.
Release Notes - VectorCAST: 6.4n
VectorCAST C, C++, Ada (Core) 53197: New column in Coverage Summary table shows the number of tests that hit that subprogram VectorCAST version 6.4n introduces a new column in the Code Coverage Summary table for Unit Test and Cover environments. For Unit Test environments, the "Test Cases Count" column displays the number of unique test cases that have hit a particular subprogram during execution. Compound tests are counted as one test regardless of the number of slots in the compound. Note: When I/O type is set to "Animation" (e.g. when using "Basis Path" coverage), the test count indicates the number of times a function is entered. This total can also include multiple slot iterations of a compound test. For Cover environments, the "Results Count" column displays the total number of coverage results that touch each subprogram. In VectorCAST/Manage, a new "Environments Count" column has been added to the Code Coverage Summary table. The column displays the number of environments contributing coverage to a subprogram. 56904: Searching for string in Coverage Viewer crashes VectorCAST when it has over 8k lines Previously, VectorCAST crashed while searching for a string in the Coverage Viewer with a source file having over eight thousand lines. This problem has been corrected in VectorCAST version 6.4n. VectorCAST no longer searches for text in the MC/DC tables unless the table has already been expanded in the Coverage Viewer.
VectorCAST/Ada: 56997: VectorCAST does not handle limited type return object; leads to harness compile error Previously, VectorCAST generated invalid code for limited records, resulting in a compile error during environment build. For example, use of a limited record type like this: type File_Name is limited record Internal_Name : Integer := 0; end record;
produced a compile error such as: "uut_interface_adacast.adb:133:49: prefix of dereference must be an access type"
VectorCAST version 6.4n allows limited record types to be declared. Because limited types cannot be copied, no processing is performed by VectorCAST. Instead, this message appears in generated test harness code: -- Cannot Invoke - Limited Record
57605: Support Ada Generic Constant Pointer Previously, VectorCAST was not able to build Ada environments for Ada generic units containing constant pointers. This problem has been fixed in VectorCAST version 6.4n.
VectorCAST/C++: 45670: x86-64 va_list fields not recognized by VectorCAST Previously, VectorCAST gave the parse error "expression must have pointer-to-struct-orunion type" when the x86-64 va_list field reg_save_area appeared in source code. In VectorCAST version 6.4n, x86-64 code is now recognized when --x86_64 is added to the parser flags. To edit the parser flags, go to the Tools => Options dialog, C/C++ tab, Language sub-tab. 49120: VectorCAST now recognizes more GNU built-in functions In VectorCAST version 6.4n, the default preprocess preinclude file for GNU 4.9 has been updated to include more definitions for GNU built-in functions. 50205: VectorCAST unable to parse GNU 5.0 x86intrin.h standard header Previously, VectorCAST gave the error "expression must have arithmetic or pointer type" when attempting to parse the GNU 5.0 standard header file x86intrin.h. This problem has been resolved in VectorCAST version 6.4n. 51104: C11 keyword _Atomic now recognized Previously, VectorCAST gave errors upon encountering the C11 keyword _Atomic. This problem has now been resolved in VectorCAST version 6.4n. 52486: VectorCAST preprocessor fails on single preprocessor token
In previous versions of VectorCAST, if a source file contained a line consisting only of "#" and the "Use VectorCAST Preprocessor" option was enabled, VectorCAST could crash. This problem is fixed in VectorCAST version 6.4n. 57298: Test Script Translator does not update array types Previously, VectorCAST's Test Script Maintenance Utility was not properly updating test cases when array types were modified. This error has been fixed in VectorCAST version 6.4n.
VectorCAST/Cover: 55354: Instrumented files appending cover I/O now touched when vcast_c_options. h changes Previously, it was difficult to tell when units appending cover I/O needed to be recompiled due to changes in the cover options file vcast_c_options.h. In VectorCAST version 6.4n, instrumented files that append cover I/O are touched when vcast_c_options.h is changed. 55582: Incorrect handling of cover results with a "." in the name Previously, VectorCAST/Cover did not properly handle dot characters (".") in result names, which could lead to duplicate results, especially when used with VectorCAST/ Manage system tests. This has been corrected in VectorCAST version 6.4n.
VectorCAST/Manage: 34418: Specialized Test Cases To test source code that contains conditional directives (for example, #if or #ifdef), the VectorCAST environment is directed to compile the source file with different configurations in order for the line group within the directives to get put into the VectorCAST environment's translation unit. As you know, a single environment for a source file can be created in VectorCAST/Manage and tested using the different configurations required to compile in the different line groups. Because the translation unit will vary based on the compiler's configuration, the test cases may need to be customized, or specialized, to a single configuration. Beginning in VectorCAST version 6.4n, it is now possible to specify that a test case be run under a specific configuration by assigning the status "Specialized test case." To assign specialized status to a test case in a Migrated environment in a Manage project, open the environment from within Manage, then right-click on the test case in the Test
Case Tree and select "Specialized" from the context menu. This test case is then visible only in the environment in that particular configuration. Once a test case is changed to "Specialized" and the environment is closed, the Diff dialog appears, showing that the Specialized test has been removed from the "common" test script and put into a new test script file. If you normally commit the .tst files to your Source Code Management, you should commit this new Specialized test script as well. 55901: Improvements to Change Impact Report VectorCAST version 6.4n provides access to both the estimated Change Impact Report for unit test and Cover environments and the Build/Execute Dry Run report for Cover environments in the same dialog. To generate the report, select a node in the Project Tree that contains the environments you want to report on. Choose Project => Change Impact Report... menu item. Choose the type of report from the two analysis radio buttons: -- Estimate impact based on source file changes (faster) This method can be used for Unit Test environments, Cover, and System Test environments. Also supports displaying the impact from changes in an alternative root source directory on tests in the Project. All tests that touch a file are considered affected by any change to that source file. This may differ from the actual action taken by incremental build/execute. The title of report is "Change Impact Report (File-based Estimate)." When generated in the GUI, the report is saved automatically in the /build/vcast_data directory. manage -p [--level=<:level>] --change-impact-report The default filename is _change_impact_report.html in the working
directory. -- Perform a full change-impact analysis (slower, Cover only) This method can be used only for System Test environments that have a system test implementation defined in the system_tests.py file. Only those tests that touch a changed function are considered affected. This method is slower due to preprocessing, but produces output matching the actual actions taken by incremental build/execute. The title of report is "Change Impact Report." When generated in the GUI, the report is
saved automatically in the /build/vcast_data directory. manage -p [--level=] --change-impact-report --fullanalysis The default filename is _manage_incremental_rebuild_report.html in the
working directory. 57201: VectorCAST does not remember Manage projects on its Recent File List using Empty Project menu item Previously, when a Manage project was created using the File => New => Manage => Empty Project menu item, the new project was not added to the File => Recent Environments menu. The problem has been corrected in VectorCAST version 6.4n.
VectorCAST/QA: 55824: Display message when build/executing and no cbt license is available Licensing affects the behavior of the build/execute commands in VectorCAST/QA. In previous versions of VectorCAST, there was no indication of the type of build/execute performed. This has been fixed in VectorCAST version 6.n. The type of build/execute will now be written out to the message window.
VectorCAST/RSP: 42627: Parser fails to recognise __bigendian and __littleendian keywords for GHS ARM Integrity and PPC Previously, VectorCAST incorrectly gave errors for Green Hills ARM and PPC source code containing the keywords __bigendian, __bytereversed, and __littleendian. This problem has been resolved in VectorCAST version 6.4n. 42697: Parser failing on unrecognized Code Composer ARM built-in functions VectorCAST now recognizes the following Code Composer ARM built-in functions: _call_swi, _disable_FIQ, _disable_interrupts,_disable_IRQ, _enable_FIQ, _enable_interrupts, _enable_IRQ, _get_CPSR, _restore_interrupts, _set_CPSR, _set_CPSR_flg, _set_interrupt_priority, __curpc, and __run_address_check.
If you have existing environments and want to use this functionality, go to the Tools => Options dialog, C/C++ tab, Misc sub-tab and set the "Preprocess preinclude file" to $(VECTORCAST_DIR)\DATA\code_composer\arm\preinclude.h.
Also, go to the Language tab and add --code_composer_version=arm to the Parser flags. These values are set by default in VectorCAST version 6.4n when the Code Composer ARM compiler is selected. 44135: Parser needs to accept _VA_LIST as argument to va_start/va_end when using --stdarg_builtin in IAR Arm v7 mode When the --stdarg_builtin parser flag was used with IAR ARM version 7, VectorCAST incorrectly reported an error on source code where a va_list type was passed as a parameter to va_start or va_end. This problem has been resolved in VectorCAST version 6.4n. 44178: Tasking C166 VX __packed__ keyword should be supported Previously, VectorCAST gave errors when reading Tasking C166 VX code containing the __packed__ keyword. This problem has been resolved in VectorCAST version 6.4n. 44874: The --stdarg_builtin parser option results in incorrect stubs for va_list types when using the IAR ARM compiler For IAR ARM version 7 and newer, use of the --stdarg_builtin parser flag caused VectorCAST to print stubs for va_list types as __builtin_va_list. Those stubs did not compile. This problem has been resolved in VectorCAST version 6.4n. 45254: Better handling of Tasking Tricore keywords __at, __far, and __interrupt The Tasking Tricode __at keyword with a value having more than one set of parentheses is now accepted in VectorCAST version 6.4n. Assignments of regular pointers to pointers to __far values are now accepted. The __interrupt keyword is now recognized. 45899: ARM intrinsic __promise should be recognized by VectorCAST, also __qadd, __qsub etc VectorCAST version 6.4n now recognizes ARM intrinsics: __breakpoint __ldrt __schedule_barrier __cdp __memory_changed __semihost __clrex __nop __sev __clz __pld __sqrt __current_pc __pldw __sqrtf __current_sp __pli __ssat __disable_fiq __promise __strex __disable_irq __qadd __strexd __enable_fiq __qdbl __strt __enable_irq __qsub __swp __fabs __rbit __usat __fabsf __rev __wfe __force_stores __return_address __wfi __ldrex __ror __yield __ldrexd
and the ARM builtin GNU functions. If you have existing ARM environments and need to use those intrinsics, go to the Tools => Options dialog, C/C++ tab, Misc sub-tab, and set the "Preprocess preinclude file" to $(VECTORCAST_DIR)\DATA\arm\preinclude.h.
50817: Parser should accept Code Composer built-in GNU functions VectorCAST gave an error when parsing Code Composer source code containing GNU builtin functions such as __builtin_fabs. This problem has been resolved in VectorCAST version 6.4n. 54255: New Ada Target options for added flexibility Previously, Ada target limitations that were built into the test harness (such as support for exceptions or delay statements) were triggered solely by the selected target. To support scenarios where 'pragma restrictions' are used, VectorCAST version 6.4n has two new Target options to control these harness build conditions. Located in the Options dialog, Target tab, the new options are: - "Target does not support exception handlers" When this option is set to True, the Ada test harness is built without exception-handling capabilities. clicast -lada options VCAST_NO_EXCEPTION_HANDLERS TRUE | FALSE
The default value is False. - "Target does not allow 'delay' statement" When this option is set to True, the Ada test harness is built with no 'delay' statements, which are typically used to make test execution for units with 'tasks' run more smoothly. clicast -lada options NO_DELAY_STATEMENTS TRUE | FALSE
The default value is False. 56978: Exception raised in range checking code for certain Ada targets On many targets, the 'image functionality is not supported, so the VectorCAST's test harness does its own numeric-to-string conversion. On some of these targets, numeric values greater than integer'last would cause constraint errors in this processing. This issue has been resolved in VectorCAST version 6.4n.
VectorCAST/Analytics: 56958: Add CBA support to Analytics In VectorCAST version 6.4n, the Analytics dashboard now includes Coverage-by-Analysis (CBA) coverage data as well as coverage data from test execution.
VectorCAST/Probe:
46640: Probe only instrumentation mode for VectorCAST/Cover VectorCAST version 6.4n introduces a new feature to product VectorCAST/Probe. In Cover environments, licensed users can apply Probe Point only instrumentation, which provides a way to insert probe points with no coverage selected. More information is available in the VectorCAST/Cover User's Guide. 56437: Probe insertion using line number VectorCAST version 6.4n introduces a new feature to product VectorCAST/Probe. In Cover environments, licensed users can define probe points in a probe point script file using a line number identifier instead of a matching line. More information is available in the VectorCAST/Cover User's Guide.
Release Notes - VectorCAST: 6.4m VectorCAST C, C++, Ada (Core) 23295: Support for VectorCAST/Lint GUI, and stand-alone project building VectorCAST version 6.4m includes a new feature, VectorCAST/Lint. This provides a familiar environment and GUI for performing analysis and viewing static analysis results from within VectorCAST. The following new clicast commands are available for creating and working with a VectorCAST/Lint Environment: Lint ENvironment Create Lint ENvironment Delete Lint ENvironment Regression_script Lint Options ADD_CPP_extension Lint Options ADD_C_extension Lint Options REMOVE_CPP_extension Lint Options REMOVE_C_extension Lint Options SET_Source_dirs path1 [path2...] [ path3 [path4...] ...] Lint Options STarting_unit_number Lint Source Add Lint Source IMport_from_repository Lint Source RECursive_add
Lint Lint Lint Lint
Source REMove Source Unit_options TOols LINT_Analyze TOols LINT_Report [
