STRIDE 4.2.01x
This page documents the changes in STRIDE version 4.2.01x (code name Hole In The Fence).
Please review this information before upgrading from an earlier version.
|
Note that if you are upgrading from a previous installation you must uninstall your existing STRIDE before installing version 4.2.01x. |
What's New
Based on customer feedback, in this release we have many key usability improvements and bug fixes.
Usability Improvements
Tests in Script
The STRIDE scripting solution has been optimized and ported to Linux.
Expectation Testing
Expectation Testing in Script and C/C++ has been enhanced to support non-strict validation.
Change Details
Fixes
This section describes defects which have been corrected in STRIDE and the customer tracking number associated with them, if any, in brackets [].
- Waiting with timeout on unordered Test Point expectation always results in a failure.
- STRIDE Runtime source may fail to compile in environment where "long long" and "long" are the same type
- Linux SDK may fail to compile in environment that has no support for SYS V semaphores.
- STRIDE Build Tools may fail to compile a test class in a namespace.
- STRIDE Runner on Linux fails to trace with timeout.
- Running a STRIDE::Test module may result in resource leaks on the target.
- Running test units in STRIDE Studio via ascript may not behave as expected.
Tests in Scripts
- STRIDE::Test module TestPointSetup method has been updated to support non-strict processing and to handle startup scenarious.
Tests in C/C++
- Expectation Tests setup API, srTestPointSetup, API has been updated to support non-strict processing and to handle startup scenarious.
Samples
- All samples were update.
Runtime
- STRIDE Host Release 4.2.01x is compatible with the Runtime Version 4.2.01
- Most of the Runtime files have been modified. It is recomended that you update them all.
- The names of the PAL OS Timer services has been renamed (from palTimerXX to palXXTimer). The signature of the timer creation API has been changed.
- All Linux SDK files have been modified.
- All Windows SDK files have been modified.
Minor and Patch releases
4.2.01a
Defects corrected and the customer tracking number associated with them, if any, in brackets []:
- Default SUID table size in the STRIDE Runtime configuration for non-complex targets is too small
- Subsequent wait on Test Points may improperly fail and cause a hang
- Test Point/Test Log timestamp calculation overflow
The following Runtime files have been modified:
srcfg.h srtest.c srtestutil.c
4.2.01b
Defects corrected and the customer tracking number associated with them, if any, in brackets []:
- Default STID table size in the STRIDE Runtime configuration for complex targets is too small
- Compilation of Windows SDK generates warnings about usage of "unsafe" CRT APIs
- Incorrect error annotation from built-in predicates in STRIDE::Test module
- In STRIDE::Test module Test Point Wait/Check methods returns no status
- In STRIDE::Test module expectation with TEST_POINT_ANY_COUNT is improperly handled
- Intercept Module generated code has a missing CALLBACK qualifier in function pointer parameters
- Crash in s2sbind while saving to a read-only output sidb file
The following Runtime files have been modified:
sr.h srapi.c srapirgl.h srapirgl.c srcfg.h srdiag.c srstid.c srtest.c srtestpp.cpp srutil.h srutil.c
The following Windows SDK files have been modified:
palcfg.h palIO.c palOS.c stride.c
4.2.01c
Defects corrected and the customer tracking number associated with them, if any, in brackets []:
- Duplicated Test Macros message in the generated report
- Incorrect calculation of struct field offsets in the Linux version of s2scompile
- Missing spaces in string data passed as arguments to remote functions of test units
- Failed to compile off-target Windows SDK using MSVC 10
The following Runtime files have been modified:
srtest.c