Release Notes - VectorCAST 5.2h (Build date 09/08/2011)

VectorCAST C,C++,Ada (Core)

18829: Unnecessary annotation of switch/case statements removed

Previously when instrumenting C/C++ "switch" statements and Ada "case" statements forBranch, Basis Paths, or MC/DC coverage, the switch/case was annotated with a branch numberin the coverage listing, even though the line was not coverable. This annotation has beenremoved in VectorCAST version 5.2h.

19020: Basis Path coverage failing for consecutive loops

Previously, VectorCAST Basis Paths Coverage would incorrectly detect path coverage whendealing with multiple loops within a single subprogram. This has been resolved in VectorCASTversion 5.2h. You may see a reduction in Basis Path coverage achieved in any source code withloops.

VectorCAST/Ada:

18923: Generic package that only contains generic subprograms does notmaintain Stub status in environment script

Previously, VectorCAST was unable to update or rebuild an environment having source codewith a generic package that contains only generic subprograms because it did not properly writethe ENVIRO.STUB line for the generic package unit to the environment script. This problemhas been fixed in VectorCAST version 5.2h.

VectorCAST/C++:

17748: Parameter input is grayed out when type is related to a type in athrow spec

Certain parameters were incorrectly grayed out in the Parameter Tree if the parameter type wasalso a member of a class of a type used in a throw specification. This problem has been fixed inVectorCAST version 5.2h.

18269: Quickparse sometimes fails on files with names that are 53characters long

In previous versions of VectorCAST, VCAST.QIK files were sometimes written incorrectly if thename of a source file contained exactly 53 characters. This could result in an environment buildfailure. This problem has been fixed in VectorCAST 5.2h.

18676: Environment builder fails when UUT contains decltype(__nullptr)

Environments for source code containing decltype(__nullptr) could not be built using VisualStudio 2010. This problem is fixed in VectorCAST version 5.2h.

18700: Incorrect parse error: "bad int kind"

VectorCAST 5.2f introduced a problem whereby VectorCAST would report a parse error on

valid code. The parse error would look like:

"vcast_preprocess.c", line 14: internal

error: type_after_integral_promotion:

bad int kind

This problem has been fixed in VectorCAST version 5.2h.

18963: Correctly instrument assignment statement containinginstantiation of non-search directory template

Previously, when instrumenting a template instantiation, where the template was defined in alibrary include path, VectorCAST did not detect the template name and determined that theinstance was actually an inequality, causing the code to be instrumented incorrectly forcoverage. This problem has been fixed in VectorCAST version 5.2h.

VectorCAST/Cover:

18713: error instrumenting function-level catch blocks

In previous versions of VectorCAST, function-level catch blocks were instrumented incorrectly.For example, consider this constructor:

C::C() try

:member(0)

{

}

catch (...)

{

}

Previously, VectorCAST would insert instrumentation into the catch block, but the code wouldnot compile.

In VectorCAST version 5.2h, function-level catch blocks are no longer instrumented. Catchblocks that are wholly within the body of a function are still instrumented as before.

VectorCAST/RSP:

17024: RSP CodeWarrior with PPC E300 Core

VectorCAST version 5.2h supports CodeWarrior for ePPC 5121.

clicast -lc template CODEWARRIOR_MPC_5121_C

clicast -lc template CODEWARRIOR_MPC_5121_CPP

18414: Testing C code on WindRiver Workbench 3.3 vxWorks 6.9 vxsimexecution failure

On vxWorks 6.9, test execution failed because the path to the windsh.scr script in VectorCASTcontained backslashes instead of forward slashes, which are required for vxWorks 6.9 or higher.This problem has been fixed in VectorCAST version 5.2h.

18618: IAR for ARM 6.21 target integration

Support for the IAR for ARM v6.21 for both the simulator and JLINK target interface has beenadded in VectorCAST version 5.2h.

clicast -lc template IAR_ARM-CORTEX_6X_SIM

clicast -lc template IAR_ARM-CORTEX_6X_SIM_CPP

clicast -lc template IAR_ARM-CORTEX_6X_JLINK

clicast -lc template IAR_ARM-CORTEX_6X_JLINK_CPP

18725: Code Composer Studio 5 (CCS 5) for ARM TM814x series

VectorCAST version 5.2h supports TI's Code Composer Studio 5 for ARM TM814x series.

clicast -lc template TI_CC_5_ARM_TM814X

clicast -lc template TI_CC_5_ARM_TM814X_CPP

18759: Allow the memory constrained HCS08 simulator to work morereliably

The 8-bit HCS08 simulator doesn't provide enough memory resources for all VectorCAST testenvironments to work because memory requirements, which are a function of the UUT codebeing tested, can exceed the available RAM of the HCS08. VectorCAST version 5.2h has beenmodified to allow the memory-constrained HCS08 simulator to work more reliably.

18869: Recognize certain Tasking c166 classic keywords without leadingunderscores

VectorCAST version 5.2h now recognizes the Tasking C166 Classic keywords bit, bitword, esfr,esfrbit, near, sfr, sfrbit, and using when they appear without a leading underscore.

18987: keil arm mdk421 has __nothrow keyword in stdio.h and thatcauses a parse error

__declspec((__nothrow)) would give an "unknown attribute" error for the Keil ARM compiler.This problem has been fixed in VectorCAST version 5.2h.

Release Notes - VectorCAST 5.2g (Build date 07/18/2011)

VectorCAST C, C++, Ada (Core)

18519: Ability to share only Custom Tools among users

VectorCAST version 5.2g supports sharing and editing of Custom Tools.

First, set the environment variable VCAST_COMMON_VCAST_QT_DIR to the location wherethe shared .vcast-qt file is to reside. When users open the VectorCAST GUI with thisenvironment variable set, they have the use of the common Custom Tools that are defined inthe shared .vcast-qt file. The shared Custom Tools are not editable unless a secondenvironment variable is set to any value: VCAST_EDIT_COMMON_OPTIONS.

If VCAST_COMMON_VCAST_QT_DIR is set but VCAST_EDIT_COMMON_OPTIONS is not,

the user's custom tools and the shared custom tools both appear, but only the user's customtools are editable.

If both are set, then only the shared custom tools are visible and editable.

export VCAST_COMMON_VCAST_QT_DIR=<path to shared .vcast-qt file>

export VCAST_EDIT_COMMON_OPTIONS=1

VectorCAST/Ada:

17751: For instrumentation need to ignore GNAT Ada lines that beginwith "#"

Previously, gnat preprocessor directives in Ada source code caused an error during coverageinstrumentation. In VectorCAST version 5.2g, this problem has been fixed. VectorCAST ignoreslines that begin with "#" when instrumenting for coverage.

17888: Environment Build error for UUT with task type with twodiscriminants

Previously, when a task type had more than one discriminant value, VectorCAST wouldincorrectly specify the values when creating the task object, resulting in a build error. Thisproblem has been resolved in VectorCAST version 5.2g.

18005: Compile error unconstrained multidimensional array is used inunit where package name is overloaded

Previously, when a Unit Under Test defined and used an unconstrained multidimensionalarray, VectorCAST could incorrectly build the object for a parameter of this type, causing acompile error. This problem has been fixed in VectorCAST version 5.2g.

18128: Parameter of Protected type from instantiation causes harnesscompile error

Previously, VectorCAST caused a compile error when building an environment for source codewhere a protected type from a generic instantiation was used as a parameter. This problem hasbeen fixed in VectorCAST version 5.2g.

18308: Configure Stubs user code not getting added to dumb stubs

Previously, Configure Stubs user code was not correctly added to units considered to be"dumb"-stubbed (units that are dependents of a stubbed unit). This has been fixed inVectorCAST version 5.2g.

18548: Overload of name STANDARD in UUT can cause compile errors ifUUT sibling name matches toplevel package

Because some users redefine base types (such as 'integer' or 'boolean'), VectorCAST usuallyadds the prefix 'standard.' before these types to indicate the types from the Standard package.Previously, this protection can fail if the user has overloaded the name 'standard' locally. Inversion 5.2g, VectorCAST now uses a rename of 'standard' for this prefix, ensuring both sets ofusers can safely build environments.

VectorCAST/C++:

17463: New environment option: Suppress Testable Functions

In VectorCAST version 5.2g, the user can prohibit VectorCAST from making a function in aUUT testable using the Suppress Testable Functions tab in the Create New EnvironmentWizard. Functions named here do not appear in the Test Case Tree nor in the <<SBF>> node ofthe Parameter Tree.

This option is specified in the environment script as:ENVIRO.SUPPRESS_TESTABLE_FUNCTION: <function name>

18050: Macros conflict with bool and string values in parameter tree

In previous versions of VectorCAST, values specified in the parameter tree for bool and stringtypes were interpreted incorrectly if a macro existed with the same name as the value specified.In VectorCAST version 5.2g, macro-based values are used only for integer and floating pointtypes.

18127: CLICAST option VCAST_DO_MCDC_ASSIGNMENTS changed toVCAST_INSTRUMENT_ASSIGNMENTS

The clicast option VCAST_DO MCDC_ASSIGNMENTS has been changed toVCAST_INSTRUMENT_ASSIGNMENTS in VectorCAST version 5.2g.

Regression scripts and CCAST_.CFG files containing the old option will continue to functionproperly, and the new option will be written to the CCAST_.CFG file.

18328: Unable to instrument coverage for operator returning "struct"

Previously, VectorCAST caused an error while instrumenting an environment using source codehaving an operator subprogram that returns a struct. The error was in the form:

"Failed to get basis path information on file: <unit>.cpp.cvrIn the vicinity of 'return' on line x column y."

This problem has been fixed in VectorCAST version 5.2g.

18386: Drag and drop functionality for adding directories in Optionsdialog, C/C++ tab, "Default directories" does not work

Previously, adding source directories by dragging from the Windows Explorer and dropping tothe Options dialog, C/C++ tab, "Default source directories for Wizard" list did not work. InVectorCAST version 5.2g, this problem has been fixed. You can drag and drop onto the "Defaultsource directories" as well as the "Source directories" in the Wizard.

VectorCAST/RSP:

17661: #error causes Keil C166 preprocess/parse to fail with no usefulerror message

Source files containing #error would cause VectorCAST to display a blank error message whenusing the Keil compiler. This problem has been fixed in VectorCAST version 5.2g.

17897: New RSP: Tasking c166 Classic compiler v8.6r2 and v7.5r5 onLinux with Trace32

VectorCAST version 5.2f implemented two new templates for Tasking C166 Classic compilers:version 8.6 and 7.5 on Linux with Trace32. In VectorCAST version 5.2g, these templates weremodified.

clicast -lc template TASKING_C166_CLASSIC_LINUX_V7.5_T32_ST10X280_SIM

clicast -lc template TASKING_C166_CLASSIC_LINUX_V7.5_T32_ST10X280_SIM_C++

andclicast -lc template TASKING_C166_CLASSIC_LINUX_V8.6_T32_XC2787X_SIM

clicast -lc template TASKING_C166_CLASSIC_LINUX_V8.6_T32_XC2787X_SIM_C++

18165: Static functions with cosmic @far directive not instrumented

Functions declared with the static preceding a Cosmic @ keyword, such as @far, did not receivecoverage instrumentation. This problem is fixed in VectorCAST version 5.2g.

18199: New RSP: Green Hills ARC Simulator

VectorCAST version 5.2g now supports GHS for ARC Simulator.

clicast -lc template ARC_GH_SIM

andclicast -lc template ARC_GH_SIM_CPP

On some GHS targets, I/O speed can be improved by reducing the buffered output to a singlewrite by setting a new option named "Dump buffer." See case 18333.

18210: Keil C51 interrupt keyword not handled by parser unless precededby a function modifier

The Keil C51 interrupt keyword was not recognized by VectorCAST unless preceded by afunction modifier, such as "small". This problem is fixed in VectorCAST version 5.2g.

18304: Add environment variable to strip Keil C51 interrupt qualifier instub-by-function file

A new option to remove the Keil C51 interrupt qualifier from functions in stub-by-function unitshas been added in VectorCAST version 5.2g. To get the new functionality, set the environmentvariable VCAST_TRANSFORM_INTERRUPT_TO_CALLABLE to any value, start VectorCAST,and rebuild any existing environments, making sure to select "sbf" and not "uut" for the unitscontaining interrupt functions. The functions will now be testable.

18333: I/O Speed Improvement

A new target option has been implemented in VectorCAST version 5.2g. Located on the Optionsdialog, Target tab, Input/Output Options sub-tab, it is called "Dump Buffer." This option isavailable only when Buffered I/O is set.

When the "dump buffer" option is set, VectorCAST will dump the test result data using a singleprintf call at the end of the test execution. On some targets, reducing the output to a single

write operation results in a dramatic speed improvement.

clicast -lc option VCAST_BUFFER_OUTPUT TRUE

clicast -lc option VCAST_DUMP_BUFFER TRUE | FALSE

The default value is false for most targets, true for GHS ARC.

18484: New RSP: Microchip MPLAB C30 for dsPIC33F simulator

VectorCAST version 5.2g supports a new template for Microchip MPLAB C30 for dsPIC33simulator.

clicast -lc template PIC_MPLABC30_DSPIC33F_SIM

Microchip MPLAB C30 for dsPIC30 and dsPIC24 are already supported, using:clicast -lc template PIC_MPLABC30_SIM

18593: Changes to template for Diab ppc target on Linux with Trace32

In VectorCAST version 5.2g, the template and .cmm scripts for Diab 5554 ppc simulator targeton linux (DIAB_LINUX_TRACE32_SIM_C) have been modified. These changes have beentested on version 5.6.0.0 of the Diab compiler.

Release Notes - VectorCAST 5.2f (Build date 06/26/2011)

VectorCAST C,C++,Ada (Core)

18281: Ability to Share VectorCAST GUI Options

In VectorCAST version 5.2f, you can set the environment variable VCAST_QT_DIR to point to adirectory where you want VectorCAST to write the .vcast-qt file. This file stores GUI settingsincluding Custom Tools, which can be then be standardized among multiple VectorCAST users.

VectorCAST/C++:

17319: TDD environments can fail to build when template-basedfunctions exist

VectorCAST caused a compile error during TDD environment build using source code havingtemplate-based functions. This problem has been fixed in VectorCAST version 5.2f.

17622: Erroneous request for parser enabler license when QAC analysisis requested with Reprise licensing

When VectorCAST was used with a version of Programming Research with the new Repriselicensing system on Windows, a FLEXlm license finder window appeared for the Analysisaction. This problem is fixed in VectorCAST version 5.2f.

17700: New Testing Method: Object File Testing

In VectorCAST version 5.2f, a new type of Testing Method is supported, called Object File

Testing. Using this method, you create an environment using the C/C++ source files as forTraditional Unit Testing, but you link in the object files (or a library containing those) for eachUUT.

In the environment script, this type of UUT is specified as:ENVIRO.OBJECT_FILE_UUT: <unit>

17946: Enum-based array index range causes test script import error

Previously, a test script import error was caused by a test script line having an array withenum-based indices in the form:

TEST.VALUE:unit.subprogram.array[0..ENUM_VALUE]:1

This problem has been fixed in VectorCAST version 5.2f.

18023: Parse error when array-style parameter is incremented like apointer

A parse error occurred while building an environment with source code having an array-styleparameter incremented like a pointer. This functionality broke with VectorCAST version 5.2abut has been fixed in version 5.2f.

VectorCAST/Cover:

12332: Support for "File Version Command" and "Notes Template" inVectorCAST/Cover

"File version command" is now supported in Cover environments in VectorCAST version 5.2f.<command to run> is executed on each unit in the environment and the results are included inthe Management Report.

clicast -lc option VCAST_FILE_VERSION_COMMAND <command to run>

"Notes Section Template" is supported in Cover environments in version 5.2f. When a testresult is opened in a Cover environment, the text from <template file> is present in the Notestab. As usual, requirements and notes are included in the Management Report.

clicast -lc option VCAST_NOTES_SECTION_TEMPLATE <path to template file>

VectorCAST/RSP:

17111: Tasking 56k _Y storage specifier on a function parameter causescompile error in harness

Environments for source code where the _Y storage specifier was applied to functionparameters did not compile using the Tasking 56k compiler. This problem is fixed inVectorCAST version 5.2f.

17884: New RSP: IAR ARM Cortex

VectorCAST version 5.2f supports IAR for ARM Cortex version 5.5 C and C++ compilers.

clicast -lc template IAR_ARM-CORTEX_55

clicast -lc template IAR_ARM-CORTEX_55_CPP

18111: Tasking C166 classic endasm pragma parameters should beaccepted by the parser

VectorCAST did not correctly parse source code with the following constructs when using theTasking C166 Classic compiler:

#pragma asm(<expression>)

#pragma asm_noflush(<expression>)

#pragma endasm(<expression>)

as well as the _bit and related keywords and intrinsic functions since they may be used to set_bit variables.

These are supported in VectorCAST version 5.2f.

18242: Static initialization of global objects does not occur in VxWorks6.3

Previously, the VectorCAST test harness caused a segmentation violation during test executionwhen using VxWorks. The error was due to static initialization of global objects failing. Thisproblem has been fixed in VectorCAST version 5.2f.

Release Notes - VectorCAST 5.2d (Build date 05/30/2011)

VectorCAST C,C++,Ada (Core)

16723: Number of digits of precision for floating point tolerance has beenincreased

Previously, VectorCAST limited the precision for floating point tolerance to 6 digits. For certainapplications, this tolerance was not precise enough. In VectorCAST version 5.2d, there is nolimit to the number of digits available when setting the environment-wide or testcase-widetolerance via CLICAST.

clicast -lc | -lada FLOATING_POINT_TOLERANCE <tolerance, using up to 255 digits of

precision>

In a test script, the testcase-wide floating point tolerance is specified using:TEST.FLOATING_POINT_TOLERANCE:<tolerance, using up to 255 digits of precision>

NOTE: For very small tolerances, the floating point representation of the value may not be exactdue to the resolution of floating point numbers; in this case, the floating point tolerance mayshow more digits than the user expects. For example, a tolerance of 0.000000001 may actuallybe displayed as 0.00000000099999.

17839: Test case tabs are not displayed in horizontally or vertically splitview

When two testcases were tiled vertically or horizontally with the GUI option "Organize

sub-windows into tabs" on, the tabs for the Parameter Tree, Notes, Execution Report etc. werebelow the edge of the window and not easily reachable. This problem has been fixed inVectorCAST version 5.2d.

17840: Wrong compound displayed when test case is dragged intocompound

Previously, when two compound test cases were open and one had been removed from theWindow grouping "TestCases", and a test case was dragged into the compound that was still inthe TestCases grouping, the the other compound test case would be brought forward in thedisplay. This problem has been fixed in VectorCAST version 5.2d.

VectorCAST/Ada:

17599: Enumeration subtypes that do not start at the first enumeralcause errors as range values

Previously, when the user specified an input range for an enumerated subtype, where thesubtype did not start at the beginning of the parent type, the range values would be storedincorrectly, causing incorrect test cases. This has been fixed in VectorCAST version 5.2d.

17940: Task bodies in stub do not put entry points in "select" loop

Previously, when building a stub for a task body, VectorCAST would just add the entry points toa simple task. This can cause problems if the entry points are called in a different order thanlisted in the task description. In VectorCAST version 5.2d, the entry points are put in a "select"loop, allowing the entry points to be called in any order.

VectorCAST/C++:

16756: Harness Initialization and Termination user code should be calledfor range data processing

Previously, running the harness to generate range data values would not run the HarnessInitialization or Termination user code. This caused issues with certain harnesses that requireddata initialization such as synchronization processing. This problem has been fixed inVectorCAST version 5.2d.

17540: Copying struct data via pointer does not copy all data

Previously, when copying and pasting the values for a structure in the Parameter tree, thestructure's pointer allocation did not expand properly and therefore the paste action was notcompleted. This problem has been fixed in VectorCAST version 5.2d.

17630: Pointers to const in user globals not allowed as input to voidpointers

In previous versions of VectorCAST, using the parameter tree to set a void* parameter to a UserGlobal could result in incorrect behavior by the harness if User Globals user code contained aglobal pointer to a const type. This problem has been fixed in VectorCAST version 5.2d.

17663: Create regression scripts is slow for certain environments

Regression scripts for some environments took a long time to generate. Speed improvementshave been made in VectorCAST version 5.2d.

17740: Exported test script is truncated when setting STL containers inparameter tree

Previously, in certain cases, VectorCAST would incorrectly export an incomplete test scriptfrom an environment using STL containers. This problem has been fixed in VectorCAST version5.2d.

17748: Parameter input is grayed out when type is related to a type in athrow spec

Certain parameters were incorrectly grayed out in the Parameter Tree if the parameter type wasalso a member of a class of a type used in a throw specification. This problem has been fixed inVectorCAST version 5.2d.

17816: Regression script ignores 'CLICAST tools cover uut_disableLEVEL_A'

The CLICAST commandclicast -lc -e<env> -u<unit> tools cover uut_disable <coverage_type>was incorrectly requiring <coverage_type> to be fully spelled out to specify the coverage type'sname. In VectorCAST version 5.2d, <coverage_type> may be any of the following (where acapital letter indicates a required character):* Statement* BRanch* Mcdc* BAsis_paths* LEVEL_A or LEVELA* LEVEL_B or LEVELB* LEVEL_C or LEVELC

17837: Do not instrument C array index expressions for code coverage

Previously, if an array index in an assignment statement used ternary notation, VectorCASTcould sometimes instrument the expression incorrectly, causing either compilation errors ortest failures. In VectorCAST version 5.2d, VectorCAST no longer instruments expressions in anarray index.

17883: Parse error for some __uuidof operators using Visual C++ 2005

The parse error "operand of __uuidof must have a class or enum type for which__declspec(uuid("...")) has been specified" was incorrectly given for some compilable codeusing Visual C++ 2005. This problem has been fixed in VectorCAST version 5.2d.

17978: Driver call to inherited function generates compile error whensubclass has data member with same name

VectorCAST caused a compile error during environment build when a call to an inheritedfunction has a data member with the same name. The compile error looks similar to:

In file included from S0000009.cpp:66:

name_conflict_expanded_driver.c: In function `void VCAST_DRIVER_9(int, char*,

char*)':

name_conflict_expanded_driver.c:547: error: `C_32415584_9->D::member' cannot be used

as a function

This problem has been fixed in VectorCAST version 5.2d.

VectorCAST/RSP:

17026: Support for Tasking Compiler for ST10

VectorCAST version 5.2d now supports the Linux-based Tasking compiler v7.5r5 for theST10x280 chip and Tasking compiler v8.6r2 for the XC2787X-200F chip, both of which use theTrace32 debugger.

17327: Error processing STDOUT mode when user code writes certaindata to standard output

When using a target that parses standard output to generate the harness output data files,VectorCAST could sometimes fail to parse the code correctly if the code under test (or usercode added to the harness) wrote data to standard output in a format that mimicked theVectorCAST output string. This problem has been fixed in VectorCAST version 5.2d.

Release Notes - VectorCAST 5.2c (Build date 04/27/2011)

VectorCAST C,C++,Ada (Core)

17206: Multi-line output from File Version Command should retainformatting

Previously, when using the File Version Command option on the Report tab with HTMLreports, the output was not formatted with appropriate line breaks. This problem has beenfixed in VectorCAST version 5.2c.

VectorCAST/Ada:

17500: Dependents of generic instantiation as UUT are not stubbed inwhitebox environment

Previously, when a generic instantiation was used as the UUT in a whitebox environment, anyunits that were referenced only in the instantiation package were not processed by VectorCAST(meaning no type support or stubbing). This has been fixed in VectorCAST version 5.2c.

VectorCAST/C++:

17254: Incorrectly generated member initializer when member is of typeunnamed enum

The member initializer in stubbed constructors was incorrect when the type was an unnamedenumeral, causing a compile error in the vcast_stubs_<unit_number>.c file. This problem isfixed in VectorCAST version 5.2c.

17391: 'Automatically clear test user code' option does not clear UserGlobals user code

In VectorCAST version 5.2c, parameter user code for the user globals unit is automaticallycleared when the Execution option "Automatically clear test user code" is set to true.

17449: New Coverage option: Treat C++ catch blocks as branches

A new configuration option has been added in VectorCAST version 5.2c. Located on theCoverage tab, it is called "Treat C++ catch blocks as branches." When set, catch blocks areconsidered to be branches for coverage purposes.

clicast -lc option VCAST_COVER_CATCH_AS_BRANCH TRUE | FALSE

The default value is true.

17493: Symbolic Constants window does not recognize parenthesis inmacro definitions

The Symbolic Constants window did not recognize macro definitions of the form:

#define CONSTANT_VALUE_1 (1)

This problem has been fixed in VectorCAST version 5.2c.

17516: Instrumentation failure with option "Instrument logicaloperations in assignment statements" and some uses of unary operators

Certain expressions containing unary operators such as '&', the address-of operator, could notbe instrumented for branch or MC/DC coverage. This problem has been fixed in VectorCASTversion 5.2c.

17520: Environment build failure when classes are mutually recursive

When source code has circular dependencies and are instantiated from a container class,VectorCAST was not able to build the test harness because one of the classes was not yetdefined. This problem has been fixed in VectorCAST version 5.2c.

17540: Copying struct data via pointer does not copy all data

Previously, when copying and pasting the values for a structure in the Parameter tree, thestructure's pointer allocation did not expand properly and therefore the paste action was notcompleted. This problem has been fixed in VectorCAST version 5.2c.

17546: Test harness stub file calls constructors that aren't defined

Previously, in the case where the test harness' stub did not specify a member initializer, whichcaused the default constructor for the base class to be used, but the default constructor was notdefined, a link error occurred. This problem has been fixed in VectorCAST version 5.2c.

17579: Rhapsody bug when launching the integration using theVectorCAST-Options

Using the VectorCAST - Options menu item from the Rhapsody integration brought up an errordialog. This problem is fixed in VectorCAST version 5.2c.

17605: Conditional operators nested inside the second or third operand ofa conditional expression are not instrumented correctly

Logical expressions inside conditional expressions were not properly instrumented for codecoverage. For example,

int var = (1 + (input1 ? 1 : 0) + (input2 ? 2 : 0) + ((input3 && !input2) ? 4 : 0));

would not receive proper code coverage due to the && operator. This problem is fixed inVectorCAST version 5.2c.

17701: Conditional operators in compound assignment statements shouldreceive coverage instrumentation like assignments

Conditional operators in compound assignment statements (operators such as +=, -=) aretreated the same ways conditional operators in assignments in VectorCAST version 5.2c.

To avoid this new behavior, set the environment variableVCAST_DONT_COVER_COMPOUND_ASSIGN to any value.

VectorCAST/RSP:

17469: Empty files #included in test harness cause compile error for SunForte

Some previously empty harness files were not compilable when using certain versions of theSun Forte compiler. These files have been updated to contain comments in VectorCAST version5.2c.&

Release Notes - VectorCAST 5.2b (Build date 03/24/2011)

VectorCAST C,C++,Ada (Core)

16129: Error compiling vcast_stdin_data.c is reported as "user code"error with no details

Previously, when VectorCAST needed to compile harness files to run a test case (when testcasedata is compiled into the harness, for example), if the compile failed, the error dialog wouldstate that the User Code compile failed, which was incorrect. In VectorCAST version 5.2b, theerror message correctly indicates that the Driver code failed to compile, and the compile errorreport is displayed as well.

16279: Test reports reflect filtering

In VectorCAST version 5.2b, reports generated when the Test Case Tree has been filtered nowindicate that the information included in the report has been reduced by the filter. In previousversions of VectorCAST, the word "<<ALL>>" was in the report, even if the information in thereport was filtered.

For example, if all subprograms but one (e.g. sub) have been hidden by the filter and a Test CaseData report is generated, the Configuration Data section now says:

This report includes data for:Unit(s) Subprogram(s) Testcase(s)unit Filtered: sub Filtered: TEST.001

The reports that indicate Filtering is in effect are:* Test Case Data report* Execution Results report* Full report

16655: Floating point tolerance not saved on individual values in a list

Previously, when specifying a list of expected values for a floating point number, when addingin-line tolerances to the list, the tolerances would be lost if the last value in the list did not havea tolerance specified. This has been fixed in VectorCAST version 5.2b.

16882: CSV and Basis Path tests need TEST.SCRIPT_FEATURE lines

The automatically-generated test scripts for basis paths test cases and CSV test cases weremissing their TEST.SCRIPT_FEATURE lines. This problem has been remedied in VectorCASTversion 5.2b.

16984: Imported basis path coverage not shown in "Save CoverageReports" report

When the coverage type was basis paths, the environment's coverage was included in thereports generated using "Save Coverage Reports", but imported coverage was not. This problemhas been fixed in VectorCAST version 5.2b.

17148: Execute With Debug from CLICAST does not allow debug ofinstrumented executable

In previous versions of VectorCAST, the clicast command to execute and start the debugger didnot allow executing the instrumented harness (UUT_INST.EXE). It always executed thenon-instrumented test harness (UUT_INTE.EXE).

In VectorCAST version 5.2b, the clicast command:

clicast -lc -e <env> -u <unit> -s <sub> -t <test> EXecute Debug [coverage]

now allows either harness to be invoked. The optional 'coverage' indicates that theinstrumented test harness executable should be used.

17263: 64-bit floating point types do not allow a user to enter a valuesmaller than 1e-255

Previously, entering a negative exponent > 255 caused a validation error, preventing the userfrom specifying the value in a test script or the GUI. This has been resolved in VectorCASTversion 5.2b.

VectorCAST/Ada:

15111: Relative paths to Parent Lib now supported in Ada Wizard

Previously, when using the Environment Wizard and browsing to the parent library,VectorCAST would convert the path to an absolute path. Relative paths were supported only iftyped directly in the edit box.

In VectorCAST version 5.2b, that page in the Wizard has an option named "Use relative paths"to indicate that the path specified using the Browse button should be full or relative to theworking directory. Typing directory in the Parent Lib edit box is no longer necessary.

On the Options dialog, Wizard tab, a new option has been implemented to indicate that youwant the Wizard to have the "Use relative paths" checkbox on by default.

clicast -lada option VCAST_USE_RELATIVE_PATHS TRUE | FALSE

The default value is false.

15508: When building harness for task types, use pointer to task ratherthan automatically creating object

Previously, when VectorCAST found a task type in a unit under test, it would create an object ofthat type to allow testing of entry points in the task. These objects could cause issues when theuser already had objects of the task type declared. In VectorCAST version 5.2b, these objectsare now pointers to the task type. When the user builds a test for the task type entry point,VectorCAST will check the pointer. If it is null, it will perform a "new" on the task. If not, it willbe assumed that the user performed the "new" via User Code (which allows modification of tasktype discriminant values as well).

16668: Cannot modify constrained subtype of an unconstrained variantrecord

Previously, when a subtype definition of a variant record specified the discriminant value,VectorCAST would not allow the user to modify an object of that subtype. In VectorCASTversion 5.2b, that limitation has been removed.

16883: Reparse whitebox capability does not work for GPR environments

For most Ada whitebox environments, setting the "Re-parse UUT for whitebox relink" optionallows the user to modify and compile their original source code and then perform anEnvironment Recompile to bring the changes into the current environment (rather thanrebuilding the environment). Previously, this mechanism did not work for GNAT environmentsbuilt from a GPR file. In VectorCAST version 5.2b this mechanism now works correctly for thisscenario.

16885: VectorCAST does not support constraining a multi-dimensionalunconstrained array

Previously, VectorCAST had no mechanism that would allow the user to constrain the range ofan unconstrained multidimensional array, such as:

type FOO_T is array ( integer range <>, integer range <> ) of integer;

In version 5.2b, VectorCAST creates objects to determine the range of each index. These objectsare only available through user code, and are referenced via the syntax:

<<unit.subprogram.parameter>>_dim Y

where dim is the alphabetic count of the dimension ("a", "b", ...), and Y is "1" for the beginningof the slice and "2" for the end of the slice.

For example, to constrain the size of a stub function that returns type FOO_T from above, theuser would add the following text to the return value user code:

<<STUB.FOO.return>>_a1 := 1;

<<STUB.FOO.return>>_a2 := 3;

<<STUB.FOO.return>>_b1 := 1;

<<STUB.FOO.return>>_b2 := 4;

which will cause the stub to return a two-dimensioned array of size 3x4.

VectorCAST/C++:

14373: Environment has compile error when VCAST_MONITOR is defined

When configuring the harness I/O functionality using macros, certain configurations caused anincorrect nesting of preprocessor directives, giving a compile error. This has been resolved inVectorCAST version 5.2b.

17233: Rhapsody OXF header file translation unit failed to parse

When using the GNU 4.3 compiler, VectorCAST would give the errors "a non-placementoperator delete must be visible in a class with a virtual destructor" and "no appropriateoperator delete is visible" for some destructors while parsing. This problem has been fixed inVectorCAST version 5.2b.

17298: designator may not specify a non-POD subobject parse error forsome GNU C++ source code

The parse error "designator may not specify a non-POD subobject" was incorrectly given incertain cases even when the source code did compile. This problem has been fixed inVectorCAST version 5.2b.

17323: void** stub parameter value not exported to test script

The values of void** parameters were incorrectly given in exported test scripts as "User codeneeded". This problem is fixed in VectorCAST version 5.2b.

If you have environments built with an earlier version of VectorCAST, you must rebuild themwith VectorCAST 5.2b prior to exporting a test script in order to get the updated behavior.

VectorCAST/Cover:

13087: Aggregate Report anomaly after removing a coverage results file

The Aggregate Coverage report on all units mistakenly included left-over coverage from anotherunit after a report for a single unit was generated and the test results were removed from theenvironment. This problem has been fixed in VectorCAST version 5.2b.

VectorCAST/RSP:

13516: PARADIGM SC520 C template needs stack length increased forsome test envs

In VectorCAST version 5.2b, the file stklen.asm has been included in the Paradigm SC520 testenvironment to allow the user to increase the stack size in the case of stack overflow.

14372: "Execute with stdout" does not support opening a file in "append"mode

Previously, when using the "stdout" mechanism for gathering harness data, the mechanism didnot support the "append" mode for opening a file. This has been resolved in VectorCASTversion 5.2b.

15449: ERC32 GNAT RSP now supports Zero Footprint run-time

The ERC32 GNAT RSP now supports the Zero Footprint (ZFP) runtime.

15818: New environment variable to strip prepended string from outputlines in Standard Output mode

When running VectorCAST in "standard output" mode (where all harness output is sent tostandard output, and VectorCAST then post-processes standard output to generate theharness output files), some targets prepend a text string to all data written to standard output.

In VectorCAST version 5.1g, a new environment variable exists to handle this case:VCAST_STDOUT_PREFIX. This variable can be set to a comma-separated list of strings. InVectorCAST version 5.2b, this environment variable no longer requires a trailing space. If any ofthe strings are found at the beginning of a line written to standard output, the text of the stringis stripped before VectorCAST tries to process the line.

For example, the harness output from the GNAAMP AAMP7 target looks something like this:VM 1 >> TESTINSS.DAT:C-000001.HAR

For VectorCAST to correctly process the output line, everything up to "TESTINSS" needs to beremoved. To do that, set the environment variableVCAST_STDOUT_PREFIX to "VM 1 >>", and then start VectorCAST.

16574: CW discrepancy between RAM mem range as definedhc12_memcfg.mem config file and linker file

When the RAM range defined in the linker file is changed to go from 0x2000 - 0x3FFF, themem config file used by the CodeWarrior simulator must also have memory defined in thatsame range. The mem config file delivered in VectorCAST version 5.2b has therefore beenupdated to extend the RAM space to include this full range.

16671: Green Hills 178B Simulator RSP not working

The integration for the Green Hills Integrity 178B simulator RSP for Ada was broken inVectorCAST version 5.1h due to changes for live-board support. This has been resolved inVectorCAST version 5.2b.

16710: GNAAMP executable name should be a constant

Starting with VectorCAST version 5.2b, when using GNAAMP, the name for the harnessexecutable will always be "UUT_INTE.AXE", rather than one name for the uninstrumentedexecutable and another name for the instrumented executable.

16763: GNAAMP "small" library does not support dynamic memoryallocation

In VectorCAST version 5.2b, the GNAAMP Runtime Support Package no longer does dynamicmemory allocation, because the aamp-small target does not support it.

Release Notes - VectorCAST 5.2a (Initial Release)

VectorCAST C,C++,Ada (Core)

13801: Flat File View in VC/Manage for Change Detection and Rebuild

A new tab has been added to the VectorCAST/Manage Project Area. This new tab is called"Files" and it displays a "file" view of the current VectorCAST/Manage project. The point of thisfeature is to allow you to see which source files are being used in the VectorCAST/Manageproject across all Test Environments and all contexts where those Test Environments exist.

By default, the files are displayed using their full directory hierarchy, and all header files aredisplayed. These display options can be controlled via a right-click menu that allows the fileview to be "flattened", and also allows you to suppress the display of header files.

In addition to allowing you to visualize the source files being used, this feature also allows youto understand which files have changed since the last time the Test Environments were builtand executed. VectorCAST/Manage can be configured to use either time-stamps (the default)or check-sums as the method of determining file changes. In the case where a TestEnvironment depends on a changed file, the Test Environment icon in the Project Tree will bedisplayed with a yellow exclamation point indicating that an update is required.

A new right-click menu option has been added to the Project Tree to allow you to easily selectall environments with source changes to dependent files. By default, VectorCAST/Manage will"scan" all dependent files for changes when a project is opened. You can also manually controlthis scanning by going to the "Files" tab and choosing "Rescan" from the right-click contextmenu.

15000: Nested compound tests are supported

VectorCAST version 5.2 now supports adding a compound test case as a slot in a compoundtest case. To do so, simply drag an existing <<COMPOUND>> test case into a new<<COMPOUND>> test case. A compound cannot be a slot of itself nor can a nested compound

have recursion.

To specify a compound test case as a slot in a compound in a test script, use syntax similar tothe following:

TEST.SUBPROGRAM:<<COMPOUND>>

TEST.NEW

TEST.NAME:<<COMPOUND>>.001

TEST.SLOT: "1", "manager", "(cl)Manager::PlaceOrder", "1",

"(CL)MANAGER::PLACEORDER.001"

TEST.END

--

TEST.SUBPROGRAM:<<COMPOUND>>

TEST.NEW

TEST.NAME:<<COMPOUND>>.002

TEST.SLOT: "1", "<<COMPOUND>>", "<<COMPOUND>>", "1", "<<COMPOUND>>.001"

TEST.END

When executing a compound test case (either nested or unnested), you will notice a change inthe Execution Report. The Event header now contains information about the compound testcase that is executing, the slot number executing, its name, and its iteration. For example, thefollowing Event header is displayed for event 1 when <<COMPOUND>>.001 (not nested) isexecuted:

Event 1<<COMPOUND>>.001 Slot 1 ((CL)MANAGER::PLACEORDER.001) Iteration 1

15053: A Find and Filter Feature has been added to the Test Case Treeand Test Editor Windows

A "Find and Filter" feature has been added to the VectorCAST/Manage Project Tree, theVectorCAST/C++ and VectorCAST/Ada Test Case Tree, and the Test Case Editor ParameterTree.br>This new functionality is accessed via the standard Ctrl-F shortcut, or the Edit -> Find mainmenu choice. Rather than using a pop-up find dialog, these windows now use a "Find Banner"at the bottom of the window. In addition to the normal find functionality, the bannerincorporates a "filter" feature. The filter feature allows a great deal of flexibility. For example,you can use this feature to prune the test tree to only those environments that have "Failed"tests.

To allow even greater control over the search, the arrow next to the Find button can be used tolimit the search/filter to a particular column in that window.

15405: Improved Status display in VectorCAST/Manage Main Project Tree

Several improvements have been made to the Project Tree in VectorCAST/Manage. Theindividual status cells now use green and red percentage bars which show the percentage statusof an individual node, as well as the accumulated status for higher-level nodes such as testsuites and platform nodes.

Previously, any status less that 100% was displayed with a red "X" and 100% was displayed as agreen check-mark. The green check-mark is maintained, but the red "X" is used only in the caseof a 0% status.br>The hover-over status for a node now shows a tabular view that is easier to understand.

A new button has been added to the "Column Options Banner" to allow you to instantly re-sizethe column widths to their default minimum widths.

15928: Additional Tab Level Added to MDI Window Area

A new GUI tab option has been added which will add another level of tabs to the VectorCASTMDI area. The new option is called: "Organize sub-window types in tabs" and is located in theGUI tab of the Tool => Options dialog.

When this option is enabled, MDI windows of the same "type" will be grouped into tabs. Forexample, Coverge Viewer windows will be organized in tabs under a main tab called "Coverage"when multiple coverage viewer windows are opened.

15975: Visual Studio C++ 2010 now supported

In addition to adding new compiler templates for Visual Studio 2010, a new start menu itemhas been added to the VectorCAST -> VectorCAST for Visual Studio program group.

16070: New Coverage option: Uncovered line indicator

A new option has been added which allows the selection of a character to be used to mark"uncovered" lines in the Coverage Viewer and coverage reports. The character can be used withStatement, DO-178B Level A, B, and C coverage types.

Located in the Tools => Options dialog, on the "Coverage" tab, and the "Options" sub-tab, thenew option is called "Uncovered line indicator." Valid character choices are: '#', '$', '%', '&', or'+'. The default is "no character", which is consistent with previous reporting.

The purpose of this new feature is to allow users to easily find uncovered lines in theVectorCAST reports outside of the VectorCAST GUI.

16201: clicast command "tools cover" now accepts multiple units

The CLICAST command to instrument a UUT or non-stubbed unit now accepts multiple units.The new syntax is:

clicast -e <env> tools cover <coverage-type> [unit_name [unit2_name...] | ALL]

The units specified on the command line are instrumented for <coverage-type>. If ALL isspecified, then all UUTs and non-stubbed units in the environment are instrumented. If nounits are specified, then only the UUTs are instrumented.

16519: New User Code Tags Tool Bar Button

A new tool-bar button has been added to allow you to open and close the "User Code Tags"window. Additionally, this window will now open in a "non-docked" mode so that it can bemoved by the user to a convenient area of the desktop.

VectorCAST/C++:

14315: Allow enumerals to be used in test cases to index into arrayssized by an enumeration type

In the case where an array is defined using an enumeral, VectorCAST will allow test cases to bebuilt using the values of the enumeration type to which the size enumeral belongs.

For example, if you have the following definitions:

enum Beverages {NoBeverage, Wine, Beer, MixedDrink, Soda};

int DrinkPrices[MixedDrink];

VectorCAST will now allow you to use the other values of the Enumeration "Beverages" as testcase index values for the array "DrinkPrices". The benefit of this feature is that it allows testcases to be completely portable in cases where enumerals are added to the enumeration typeafter the VectorCAST test cases have been created.

The enumerals will be displayed in the Test Case Editor, the Test Case Scripts, and theExecution Reports.

To disable this feature, use the Builder tab option: "Disable direct array indexing" or fromclicast, use the following command:

clicast -lc option VCAST_DISABLE_DIRECT_ARRAY_INDEXING True

The default value is False.

15791: Macros and global constants can be used as Test Case Input orExpected Values

VectorCAST version 5.2 provides a data dictionary for numeric macros or global constants thatare defined in any of the Units Under Test or their header dependencies. These integer andfloating-point symbolic constants are detected during the environment build process and willbe available in the "Symbolic Constants" Window. The window contains four columns: themacro or variable name, value, numeric base, and base data type (int or float).

The "Symbolic Constants" Window is accessed by clicking on the "#" icon in the tool bar. Bydefault it is diplayed "undocked" but may be docked in the MDI area. You can use a symbolicconstant as an Input or Expected Value by dragging from the Symbolic Constants window anddropping into the Parameter Tree, or by typing its name in the Parameter Tree.

You will notice that when you select a particular Symbolic Constant, the Test Case Editorwindow colorizes the data items that match the type of the selected constant.