This release note covers the changes between v2.0r1 and v3.0r1 of the TASKING Safety Checker. For release notes prior to v3.0r1, please visit the Safety Checker support website.
TASKING Safety Checker is an (A)SIL, (Automotive) Safety Integrity Level, aware Static Analyzer which supports Software Partitioning and helps to assure Freedom from Interference between software with incompatible (A)SILs.
Beside isolation of code and data, the Safety Checker is also capable of checking C source code (ISO/IEC 9899:1990, 1999, 2011 and 2017) for possible vulnerabilities, including MISRA C guidelines (1998, 2004 and 2012) and CERT C secure coding standard.
For Windows, the Safety Checker will be installed in the 'Program Files' folder by default. This folder has only limited write access, so in general it is not possible to run the examples from within this location. Installing the Safety Checker outside the 'Program Files' folder solves this problem, but just copying the whole example folder to a location with sufficient access rights is preferable.
The distributed Eclipse plugin for the TASKING Safety Checker only supports Eclipse versions 4.21 and higher. Eclipse versions distributed with some of the TASKING products are not supported. Please, either use Eclipse distributed with the TASKING SmartCode product or newer Eclipse versions.
All executable files in this release have the following build number: Build 23071342.
This section gives an overview of the most important new features and improvements in TASKING Safety Checker v3.0r1.
Special #pragma safe_access was added to mark analyzed complex cases that are safe but
still produce access violation errors.
It hides false-positive errors in the report making it more readable and actable on.
External call report generation was implemented to show all functions unavailable for analysis. It shows all the functions that should be manually analyzed and all the functions that execute them and thus could be affected in one place. Eliminating groups of known safe external calls instead of going through such calls one by one reduces manual verification efforts.
To simplify work of project analysis configuration setup, a GUI Eclipse plugin was created. Plugin features quality-of-life improvements, including:
The analysis of some pointer manipulations has been improved significantly based on real world projects. It significantly reduces a number of W799 warnings ('unable to check safety violation') thus reducing manual verification efforts.
Optimization of how analysis works with aliased elements and other changes were made to reduce the amount of memory and processing power needed for the analysis. Support for larger project analysis is thus significantly improved.
For a quick start, go to the Start menu and open the 'TASKING Safety Checker User Guide' from within the sub-folder called 'Manuals'. After reading chapter 'Introduction', chapter 'Tutorial' is a good starting point for exploring the capabilities of the Safety Checker.
TASKING products are protected with TASKING license management software.
You need a license key when you install a TASKING product on a computer. When you order a TASKING product from TASKING or one of its distributors, a license key will be sent to you by email or on paper.
See Obtaining a License on our website for more information.
If you have ordered a TASKING product with a floating license, you can have it serviced by a Remote License Server (the most convenient solution) or through a Local License Server (in case you have no external network access for example). Consult your TASKING representative for assistance on deciding what the best setup would be for your situation.
If you like to setup up a local license server, we kindly refer you for more information to Support for TASKING License Management System (TLM) on our website. Here you can also download the TASKING Local License Server package.
It is advised that you install the TASKING Local License Server before you install products that require this server.