MATLAB. Polyspace Code Prover. User's Guide
Book information
Description
Introduction About This User's Guide Configure Analysis on Desktop Run Polyspace Analysis on Desktop Add Source Files for Analysis in Polyspace Desktop User Interface Add Sources from Build Command Add Sources Manually Run Analysis in Polyspace Desktop User Interface Arrange Layout of Windows for Project Setup Set Product and Result Location Start and Monitor Analysis Fix Compilation Errors Open Results Contents of Polyspace Project and Results Folders File Organization Files in the Results Folder Storage of Temporary Files During Polyspace Analysis Create Polyspace Projects from Visual Studio Build Create Polyspace Project from Build in Visual Studio Developer Prompt Create Polyspace Project from Build in Visual Studio IDE Create Project in Polyspace Desktop User Interface Using Configuration Template Why Use Templates Use Predefined Template Create Your Own Template Sharing Project Templates Update Project in Polyspace Desktop User Interface Change Folder Path Refresh Source List Refresh Project Created from Build Command Add Source and Include Folders Manage Include File Sequence Modularize Large Projects in Polyspace Desktop User Interface Organize Layout of Polyspace Desktop User Interface Create Your Own Layout Save and Reset Layout Customize Polyspace Desktop User Interface Possible Customizations Storage of Polyspace User Interface Customizations Upload Results to Polyspace Access Upload Results from Polyspace Desktop Client Upload Results at Command Line Results Upload Compatibility and Permissions Run Polyspace Analysis with Windows or Linux Scripts Run Polyspace Analysis from Command Line Specify Sources and Analysis Options Directly Specify Sources and Analysis Options in Text File Create Options File from Build System Modularize Polyspace Analysis by Using Build Command Build Source Code Create One Polyspace Options File for Full Build Create Options File for Specific Binary in Build Command Create One Options File Per Binary Created in Build Command polyspace-configure Source Files Selection Syntax Modularize Polyspace Analysis at Command Line Based on an Initial Interdependency Analysis Basic Options Constrain Module Complexity During Partitioning Result Folder Names Forbid Cycles in Module Dependence Graph Configure Polyspace Analysis Options in User Interface and Generate Scripts Prerequisites Generate Scripts from Configuration Run Analysis with Generated Scripts Run Polyspace Analysis with MATLAB Scripts Integrate Polyspace with MATLAB and Simulink Integrate Polyspace with MATLAB or Simulink from Same Release Integrate Polyspace with MATLAB or Simulink Installation from Earlier Release Check Integration Between MATLAB and Polyspace Get Started with Polyspace Analysis by Using MATLAB Prerequisites Run Polyspace Analysis by Using MATLAB Frequently Used MATLAB Functions Run Polyspace Analysis by Using MATLAB Scripts Prerequisites Specify Multiple Source Files Check for MISRA C:2012 Violations Check for Specific Defects or Coding Rule Violations Find Files That Do Not Compile Run Analysis on Server Compare Results from Different Polyspace Runs by Using MATLAB Scripts Review Only New Results Compared to Last Run Review New Results and Unreviewed Results from Last Run Generate MATLAB Scripts from Polyspace User Interface Prerequisites Create Scripts from Polyspace Projects Troubleshoot Polyspace Analysis from MATLAB Prerequisites Capture Polyspace Analysis Errors in Error Log Run Polyspace Analysis in Simulink Run Polyspace Analysis on Code Generated with Embedded Coder Prerequisites Generate and Analyze Code Review Analysis Results Annotate Blocks to Justify Issues Changes in Polyspace Analysis Workflows in Simulink in R2019b Code Verification Workflow in a Nutshell Locate Pre-R2019b Menu Items in Simulink Toolstrip Run Polyspace on Code Generated by Using Previous Releases of Simulink Prerequisite Run a Cross-Release Polyspace Analysis Review Results Run Polyspace Analysis on Code Generated from Simulink Model Prerequisites Open Model for Code Generation and Polyspace Analysis Generate and Analyze Code Review Analysis Results Trace Errors Back to Model and Fix Them Check for Coding Rule Violations Annotate Blocks to Justify Results Fix Model Design Issues Found as Bugs in Generated Code Prerequisites Open Model with Stateflow Chart Containing Design Issues Generate and Analyze Code Fix Issues Run Polyspace Analysis on Generated Code by Using Packaged Options Files Generate and Package Polyspace Options Files Run Polyspace Analysis by Using the Packaged Options Files Run Polyspace Analysis on Custom Code in Simulink Models Prerequisite Analyze Custom Code Review Analysis Results Run Polyspace Analysis on S-Function Code Prerequisites S-Function Analysis Workflow Compile S-Functions to Be Compatible with Polyspace Example S-Function Analysis Run Polyspace Analysis on Custom Code in C Caller Blocks and Stateflow Charts Prerequisites C/C++ Function Called Once in Model C/C++ Function Called Multiple Times in Model Run Polyspace Analysis on Custom Code in C Function Block Prerequisites Open Model for Running Polyspace Analysis on Custom Code in C Function Block Run Polyspace Analysis Identify Issues in C Code Fix Identified Issues Recommended Model Configuration Parameters for Polyspace Analysis Configure Advanced Polyspace Options in Simulink Configure Options Share and Reuse Configuration How Polyspace Analysis of Generated Code Works Default Polyspace Options for Code Generated with Embedded Coder Default Options Constraint Specification Recommended Polyspace options for Verifying Generated Code Hardware Mapping Between Simulink and Polyspace External Constraints on Polyspace Analysis of Generated Code Extract External Constraints from Model Storage Classes Supported for Constraint Extraction From Simulink Model Specify Custom External Constraints Run Polyspace Analysis on Code Generated with TargetLink Configure and Run Analysis Review Analysis Results Default Polyspace Options for Code Generated with TargetLink TargetLink Support Default Options Lookup Tables Data Range Specification Code Generation Options Troubleshoot Navigation from Code to Model Links from Code to Model Do Not Appear Links from Code to Model Do Not Work Your Model Already Uses Highlighting Polyspace Support of MATLAB and Simulink from Different Releases Complete Integration Cross-Release Integration Partial Integration Navigate Back to Model Run Polyspace Analysis in MATLAB Coder Run Polyspace on C/C++ Code Generated from MATLAB Code Prerequisites Run Polyspace Analysis Review Analysis Results Run Analysis for Specific Design Range Configure Advanced Polyspace Options in MATLAB Coder App Configure Options Share and Reuse Configuration Running Polyspace on AUTOSAR Code Using Polyspace in AUTOSAR Software Development Check if Implementation of Software Components Follow Specifications Assess Impact of Edits to Specifications Check Code Implementation for Run-time Errors and Mismatch with Specifications Check Code Implementation Against Specification Updates Choose Between Component-Based and Integration Analysis of AUTOSAR Code with Polyspace Definitions Similarities and Differences Choosing Between Component-Based and Integration Analysis Benefits of Polyspace for AUTOSAR Polyspace Modularizes Analysis Based on AUTOSAR Components Polyspace Detects Mismatch Between Code and AUTOSAR XML Spec Run Polyspace on AUTOSAR Code Run Polyspace in User Interface Run Polyspace Using Scripts Select AUTOSAR XML (ARXML) and Code Files for Polyspace Analysis Adapt Linux find Command to Select Files File Selection Options File Selection Examples Root Folder Specification Troubleshoot Polyspace Analysis of AUTOSAR Code View Project Completion Status View Errors in AUTOSAR XML Parsing View Compilation Errors in Code Interpret Errors and Warnings in Polyspace Analysis of AUTOSAR Code Overview of File Structure See File Selections Run Analysis Interpret Warnings Run Polyspace on AUTOSAR Code with Conservative Assumptions Run Polyspace on AUTOSAR Code Using Build Command Run Code Prover Without Compilation Options Run Code Prover with Compilation Options from Build Command Run Polyspace Analysis in IDE Plugins Run Polyspace Analysis on Eclipse Projects Configure and Run Analysis Review Analysis Results Specify Polyspace Compiler Options Through Eclipse Project Eclipse Refers Directly to Your Compilation Toolchain Eclipse Uses Your Compilation Toolchain Through Build Command Configure Analysis on Server Run Polyspace Analysis on Servers Run Polyspace Code Prover on Server and Upload Results to Web Interface Prerequisites Check Polyspace Installation Run Code Prover on Sample Files Sample Scripts for Code Prover Analysis on Servers Specify Sources and Options in Separate Files from Launching Scripts Complete Workflow Send Email Notifications with Polyspace Code Prover Server Results Creating E-mail Notifications Prerequisites Export Results for E-mail Attachments Assign Owners and Export Assigned Results Offload Polyspace Analysis from Continuous Integration Server to Another Server Install Products Configure and Start Job Scheduler Services on Head Node and Worker Node Offload Analysis from Client Node Sample Scripts for Polyspace Analysis with Jenkins Extending Sample Scripts to Your Development Process Prerequisites Set Up Polyspace Plugin in Jenkins Script to Run Bug Finder, Upload Results and Send Common Notification Script to Run Bug Finder, Upload Results and Send Personalized Notification Sample Jenkins Pipeline Scripts for Polyspace Analysis Prerequisites Run Polyspace Analysis in Stages in a Pipeline Script Integrate Polyspace Server Products with MATLAB Integrate Polyspace Server Products with MATLAB Check Integration Between MATLAB and Polyspace Run Polyspace Server Products with MATLAB Scripts Configure Job Submissions from Desktop to Server Offload Polyspace Analysis to Remote Servers from Desktop Send Polyspace Analysis from Desktop to Remote Servers Client-Server Workflow for Running Analysis Prerequisites Offload Analysis in Polyspace User Interface Send Polyspace Analysis from Desktop to Remote Servers Using Scripts Client-Server Workflow for Running Analysis Prerequisites Run Remote Analysis Manage Remote Analysis Sample Scripts for Remote Analysis Configuration Workflows Common to All Platforms Configure Polyspace Analysis Specify Polyspace Analysis Options Polyspace User Interface Windows or Linux Scripts MATLAB Scripts Eclipse and Eclipse-based IDEs Simulink MATLAB Coder App Options Files for Polyspace Analysis What are Options Files Specifying Options Files Specifying Multiple Options Files Configure Target and Compiler Options Specify Target Environment and Compiler Behavior Extract Options from Build Command Specify Options Explicitly C/C++ Language Standard Used in Polyspace Analysis Supported Language Standards Default Language Standard C11 Language Elements Supported in Polyspace C++11 Language Elements Supported in Polyspace C++14 Language Elements Supported in Polyspace C++17 Language Elements Supported in Polyspace Provide Standard Library Headers for Polyspace Analysis Create Polyspace Analysis Configuration from Build Command (Makefile) Requirements for Project Creation from Build Systems Compiler Requirements Build Command Requirements Supported Keil or IAR Language Extensions Special Function Register Data Type Keywords Removed During Preprocessing Remove or Replace Keywords Before Compilation Remove Unrecognized Keywords Remove Unrecognized Function Attributes Gather Compilation Options Efficiently Configure Inputs and Stubbing Options Specify External Constraints Create Constraint Template Create Constraint Template from Code Prover Analysis Results Update Existing Template Specify Constraints in Code External Constraints for Polyspace Analysis Constraint Specification Constraint Specification Limitations Constrain Global Variable Range User Interface (Desktop Products Only) Command Line Constrain Function Inputs User Interface (Desktop Products Only) Command Line XML File Format for Constraints Syntax Description — XML Elements Valid Modes and Default Values Configure Multitasking Analysis Analyze Multitasking Programs in Polyspace Configure Analysis Review Analysis Results Auto-Detection of Thread Creation and Critical Section in Polyspace Multitasking Routines that Polyspace Can Detect Example of Automatic Thread Detection Naming Convention for Automatically Detected Threads Limitations of Automatic Thread Detection Configuring Polyspace Multitasking Analysis Manually Specify Options for Multitasking Analysis Adapt Code for Code Prover Multitasking Analysis Protections for Shared Variables in Multitasking Code Detect Unprotected Access Protect Using Critical Sections Protect Using Temporally Exclusive Tasks Protect Using Priorities Protect By Disabling Interrupts Define Atomic Operations in Multitasking Code Nonatomic Operations What Polyspace Considers as Nonatomic Define Specific Operations as Atomic Define Preemptable Interrupts and Nonpreemptable Tasks Emulating Task Priorities Examples of Task Priorities Further Explorations Define Critical Sections with Functions That Take Arguments Polyspace Assumption on Functions Defining Critical Sections Adapt Polyspace Analysis to Lock and Unlock Functions with Arguments Configure Coding Rules Checking and Code Metrics Computation Check for Coding Standard Violations Configure Coding Rules Checking Review Coding Rule Violations Generate Reports Avoid Violations of MISRA C:2012 Rules 8.x Software Quality Objective Subsets (C:2004) Rules in SQO-Subset1 Rules in SQO-Subset2 Software Quality Objective Subsets (AC AGC) Rules in SQO-Subset1 Rules in SQO-Subset2 Software Quality Objective Subsets (C:2012) Guidelines in SQO-Subset1 Guidelines in SQO-Subset2 Software Quality Objective Subsets (C++) SQO Subset 1 – Direct Impact on Selectivity SQO Subset 2 – Indirect Impact on Selectivity Coding Rule Subsets Checked Early in Analysis MISRA C:2004 and MISRA AC AGC Rules MISRA C:2012 Rules Create Custom Coding Rules User Interface (Desktop Products Only) Command Line Compute Code Complexity Metrics Impose Limits on Metrics (Desktop Products Only) Impose Limits on Metrics (Server and Access products) HIS Code Complexity Metrics Project File Function Migrate Code Prover Workflows for Checking Coding Standards and Code Metrics to Bug Finder Changes in Workflow Polyspace Support for Coding Standards Summary of Polyspace Support AUTOSAR C++14 MISRA C++:2008 MISRA C:2012 CERT C Other Coding Rule Sets and Concepts Polyspace MISRA C:2004 and MISRA AC AGC Checkers MISRA C:2004 and MISRA AC AGC Coding Rules Supported MISRA C:2004 and MISRA AC AGC Rules Troubleshooting List of Supported Coding Rules Unsupported MISRA C:2004 and MISRA AC AGC Rules Polyspace MISRA C:2012 Checkers Required or Mandatory MISRA C:2012 Rules Supported by Polyspace Bug Finder Mandatory Rules Required Rules Statically Enforceable MISRA C:2012 Rules Supported by Polyspace Bug Finder Essential Types in MISRA C:2012 Rules 10.x Categories of Essential Types How MISRA C:2012 Uses Essential Types Unsupported MISRA C:2012 Guidelines Required and Statically Enforceable CERT C Rules Supported by Polyspace Bug Finder Polyspace MISRA C++ Checkers Unsupported MISRA C++ Coding Rules Language Independent Issues General Lexical Conventions Expressions Declarations Classes Templates Exception Handling Library Introduction Required MISRA C++:2008 Coding Rules Supported by Polyspace Bug Finder Supported Rules Unsupported Rules Polyspace JSF AV C++ Checkers JSF AV C++ Coding Rules Supported JSF C++ Coding Rules Unsupported JSF++ Rules Required AUTOSAR C++14 Coding Rules Supported by Polyspace Bug Finder Supported Rules Unsupported Rules Statically Enforceable AUTOSAR C++14 Rules Supported by Polyspace Bug Finder Automated Rules Partially Automated Rules Configure Verification of Modules or Libraries Provide Context for C Code Verification Control Variable Range Control Function Call Sequence Control Stubbing Behavior Provide Context for C++ Code Verification Control Variable Range Control Function Call Sequence Verify C Application Without main Function Generate main Function Manually Write main Function Verify C++ Classes Verification of Classes Methods and Class Specifics Configure Code Prover Run-Time Checks Modify or Disable Code Prover Run-Time Checks Integer Overflow Floating Point Overflow Initialization Library Functions Pointers Unreachable Code or Dead Code Configure Comment Import from Previous Results Import Review Information from Previous Polyspace Analysis Automatic Import from Last Analysis Import from Another Analysis Result Import Algorithm View Imported Review Information That Does Not Apply Import Existing MISRA C: 2004 Justifications to MISRA C: 2012 Results Mapping Multiple MISRA C: 2004 Annotations to the Same MISRA C: 2012 Result Review Results in Polyspace User Interface Interpret Polyspace Code Prover Results Interpret Code Prover Results in Polyspace Desktop User Interface Interpret Result Find Root Cause of Result Dashboard in Polyspace Desktop User Interface Code Covered by Verification Check Distribution Top 5 Orange Sources Top 5 Coding Rule Violations Other Dashboard Features Concurrency Modeling in Polyspace Desktop User Interface Results List in Polyspace Desktop User Interface Source Code in Polyspace Desktop User Interface Examine Source Code View Variable Ranges View Extent of Code Block Manage Multiple Files Expand and Collapse Macros See Function Callers and Callees Result Details in Polyspace Desktop User Interface View Traceback View Error Call Graph View Call Hierarchy and Variable Access Call Hierarchy in Polyspace Desktop User Interface Show or Hide Callers and Callees Navigate Call Hierarchy Determine if Function is Stubbed See Entire Call Hierarchy of Program Variable Access in Polyspace Desktop User Interface View Access Graph View Structured Variables View Operations on Anonymous Variables View Access Through Global Pointers Show or Hide Callers and Callees Show or Hide Accesses in Unreachable Code Other Features Reviewing Checks Review and Fix Absolute Address Usage Checks Review and Fix Correctness Condition Checks Step 1: Interpret Check Information Step 2: Determine Root Cause of Check Step 3: Trace Check to Polyspace Assumption Review and Fix Division by Zero Checks Step 1: Interpret Check Information Step 2: Determine Root Cause of Check Step 3: Look for Common Causes of Check Step 4: Trace Check to Polyspace Assumption Review and Fix Function Not Called Checks Step 1: Interpret Check Information Step 2: Determine Root Cause of Check Step 3: Look for Common Causes of Check Review and Fix Function Not Reachable Checks Step 1: Interpret Check Information Step 2: Determine Root Cause of Check Review and Fix Function Not Returning Value Checks Step 1: Interpret Check Information Step 2: Determine Root Cause of Check Review and Fix Illegally Dereferenced Pointer Checks Step 1: Interpret Check Information Step 2: Determine Root Cause of Check Step 3: Look for Common Causes of Check Step 4: Trace Check to Polyspace Assumption Review and Fix Incorrect Object Oriented Programming Checks Step 1: Interpret Check Information Step 2: Determine Root Cause of Check Review and Fix Invalid C++ Specific Operations Checks Step 1: Interpret Check Information Step 2: Determine Root Cause of Check Step 3: Trace Check to Polyspace Assumption Review and Fix Invalid Shift Operations Checks Step 1: Interpret Check Information Step 2: Determine Root Cause of Check Step 3: Look for Common Causes of Check Step 4: Trace Check to Polyspace Assumption Review and Fix Invalid Use of Standard Library Routine Checks Step 1: Interpret Check Information Step 2: Trace Check to Polyspace Assumption Invalid Use of Standard Library Floating Point Routines What the Check Looks For Single-Argument Functions Checked Functions with Multiple Arguments Review and Fix Non-initialized Local Variable Checks Step 1: Interpret Check Information Step 2: Determine Root Cause of Check Step 3: Look for Common Causes of Check Step 4: Trace Check to Polyspace Assumption Review and Fix Non-initialized Pointer Checks Step 1: Interpret Check Information Step 2: Determine Root Cause of Check Step 3: Trace Check to Polyspace Assumption Review and Fix Non-initialized Variable Checks Step 1: Interpret Check Information Step 2: Determine Root Cause of Check Step 3: Trace Check to Polyspace Assumption Review and Fix Non-Terminating Call Checks Step 1: Determine Root Cause of Check Step 2: Look for Common Causes of Check Identify Function Call with Run-Time Error Review and Fix Non-Terminating Loop Checks Step 1: Interpret Check Information Step 2: Determine Root Cause of Check Step 3: Look for Common Causes of Check Identify Loop Operation with Run-Time Error Review and Fix Null This-pointer Calling Method Checks Step 1: Interpret Check Information Step 2: Determine Root Cause of Check Review and Fix Out of Bounds Array Index Checks Step 1: Interpret Check Information Step 2: Determine Root Cause of Check Step 3: Look for Common Causes of Check Step 4: Trace Check to Polyspace Assumption Review and Fix Overflow Checks Step 1: Interpret Check Information Step 2: Determine Root Cause of Check Step 3: Look for Common Causes of Check Step 4: Trace Check to Polyspace Assumption Detect Overflows in Buffer Size Computation Review and Fix Return Value Not Initialized Checks Step 1: Interpret Check Information Step 2: Determine Root Cause of Check Step 3: Look for Common Causes of Check Step 4: Trace Check to Polyspace Assumption Review and Fix Uncaught Exception Checks Step 1: Interpret Check Information Step 2: Determine Root Cause of Check Review and Fix Unreachable Code Checks Step 1: Interpret Check Information Step 2: Determine Root Cause of Check Step 3: Look for Common Causes of Check Review and Fix User Assertion Checks Step 1: Determine Root Cause of Check Step 2: Look for Common Causes of Check Step 3: Trace Check to Polyspace Assumption Find Relations Between Variables in Code Insert Pragma to Determine Variable Relation Further Exploration Review Polyspace Results on AUTOSAR Code Open Results See Overview of Results for all Software Components See Runnables and Source Files in Software Component Interpret AUTOSAR Specific Run-time Checks for Software Component Fix or Comment Polyspace Results Address Polyspace Results Through Bug Fixes or Justifications Add Review Information to Results File Comment or Annotate in Code Manage Results Filter and Group Results in Polyspace Desktop User Interface Filter Results Group Results Prioritize Check Review Generate Reports from Polyspace Results Generate Reports from Polyspace Results Generate Reports from User Interface Generate Reports from Command Line Export Polyspace Analysis Results Export Results to Text File Export Results to MATLAB Table Export Results to JSON Format View Exported Results Export Polyspace Analysis Results to Excel by Using MATLAB Scripts Report Result Summary and Details in One Worksheet Control Formatting of Excel Report Export Global Variable List Export Variable List to Text File Export Variable List to MATLAB Table View Exported Variable List Visualize Code Prover Analysis Results in MATLAB Export Results to MATLAB Table Generate Graphs from Results and Include in Report Customize Existing Code Prover Report Template Prerequisites View Components of Template Change Components of Template Further Exploration Sample Report Template Customizations Add List of Recursive Functions Show Red Run-Time Checks Only Show Non-Justified Run-Time Checks Only Add Chapter for Functional Design Errors Review Results on Web Browser Interpret Polyspace Code Prover Access Results Interpret Code Prover Results in Polyspace Access Web Interface Interpret Result Find Root Cause of Result Dashboard in Polyspace Access Web Interface Code Metrics Dashboard in Polyspace Access Web Interface Quality Objectives Dashboard in Polyspace Access Web Interface Customize Software Quality Objectives Results List in Polyspace Access Web Interface Source Code in Polyspace Access Web Interface Tooltips Examine Source Code Expand Macros View Code Block Navigate from Code to Model Result Details in Polyspace Access Web Interface Call Hierarchy in Polyspace Access Web Interface Configuration Settings in Polyspace Access Web Interface Global Variables in Polyspace Access Web Interface Review History in Polyspace Access Web Interface Create and Track Issue in Bug Tracking Tool from Polyspace Access Web Interface Create a Ticket Manage Existing Tickets Fix or Comment Polyspace Results on Web Browser Address Results in Polyspace Access Through Bug Fixes or Justifications Add Review Information in Result Details pane Comment or Annotate in Code Merge Review Information Between Polyspace Access Projects Manage Results Manage Permissions and View Project Trends in Polyspace Access Web Interface Create a Project Folder Manage Project Permissions View Project Trends Filter and Sort Results in Polyspace Access Web Interface Filter Results Create Custom Filter Groups in Polyspace Access Web Interface Prioritize Check Review in Polyspace Access Web Interface Compare Results in Polyspace Access Project to Previous Runs and View Trends Comparison Mode Export Results from Polyspace Access Web Server Open or Export Results from Polyspace Access Open Polyspace Access Results in a Desktop Interface Export Polyspace Access Results to a TSV File Review Workflows Common to All Platforms Hide Known or Acceptable Results Using Code Annotations Annotate Code and Hide Known or Acceptable Results Code Annotation Syntax Syntax Examples Code Annotation Warnings Short Names of Code Prover Run-Time Checks Short Names of Code Complexity Metrics Project Metrics File Metrics Function Metrics Annotate Code for Known or Acceptable Results (Not Recommended) Add Annotations from the Polyspace Interface Add Annotations Manually Define Custom Annotation Format Define Annotation Syntax Format Map Your Annotation to the Polyspace Annotation Syntax Define Multiple Custom Annotation Syntaxes Annotation Description Full XML Template Example Advanced Review Workflows Evaluate Polyspace Code Prover Results Against Software Quality Objectives Specifications of SQO Levels Compare Verification Results Against Software Quality Objectives Customize SQO Levels Justify Coding Rule Violations Using Code Prover Checks Rules About Data Type Conversions Rules About Pointer Arithmetic Polyspace Results in Lines Containing Macros Macros in Source Lines Can Be Expanded in Place Results in Function-Like Macros Shown Only Once Migrate Results from Polyspace Metrics to Polyspace Access Requirements for Migration Migration of Results Differences in SQO Between Polyspace Metrics and Polyspace Access Understanding Code Prover Results Code Prover Checks and Source Code Tooltips Code Prover Result and Source Code Colors Result Colors Source Code Colors Global Variable Colors Code Prover Run-Time Checks Data Flow Checks Numerical Checks Static Memory Checks Control Flow Checks C++ Checks Other Checks Code Prover Analysis Following Red and Orange Checks Code Following Red Check Green Check Following Orange Check Gray Check Following Orange Check Red Check Following Orange Check Red and Green Checks in Unreachable Code Order of Code Prover Run-Time Checks Variable Ranges in Source Code Tooltips After Code Prover Analysis Why Code Prover Reports Ranges on Variables Why Variable Ranges Can Sometimes Be Narrower Than Expected Orange Checks in Polyspace Code Prover Orange Checks in Polyspace Code Prover When Orange Checks Occur Why Review Orange Checks How to Review Orange Checks How to Reduce Orange Checks Managing Orange Checks in Polyspace Code Prover Software Development Stage Quality Goals Critical Orange Checks in Polyspace Code Prover How to See Only Critical Checks Which Orange Checks Are Considered Critical Limit Display of Orange Checks in Polyspace Desktop User Interface Reduce Orange Checks in Polyspace Code Prover Provide Context for Verification Improve Verification Precision Follow Coding Rules Reduce Application Size Troubleshooting Troubleshooting in Polyspace Code Prover View Error Information When Analysis Stops View Error Information in User Interface View Error Information in Log File Troubleshoot Compilation and Linking Errors Issue Possible Cause: Deviations from Standard Possible Cause: Linking Errors Possible Cause: Conflicts with Polyspace Function Stubs Reduce Memory Usage and Time Taken by Polyspace Analysis Issue Possible Cause: Temporary Folder on Network Drive Possible Cause: Anti-Virus Software Possible Cause: Large and Complex Application Possible Cause: Too Many Entry Points for Multitasking Applications Identify Root Causes of Code Prover Red or Orange Checks Issue Possible Cause: Relation to Prior Code Operations Possible Cause: Software Assumptions Contact Technical Support About Issues with Running Polyspace Provide System Information Provide Information About the Issue Fix Error: Polyspace Cannot Find Server Message Possible Cause Solution Fix Error: Job Manager Cannot Write to Database Message Possible Cause Workaround Create Polyspace Projects from Build Systems That Use Unsupported Compilers Issue Cause Solution Fix Slow Build Process When Polyspace Traces Build Issue Cause Solution Check if Polyspace Supports Build Scripts Issue Possible Cause Solution Troubleshoot Project Creation from MinGW Build Issue Cause Solution Troubleshoot Project Creation from Visual Studio Build Resolve polyspace-autosar Error: Could Not Find Include File Issue Solution Resolve polyspace-autosar Error: Conflicting Universal Unique Identifiers (UUIDs) Issue Solution Resolve polyspace-autosar Error: Data Type Not Recognized Issue Solution Fix Polyspace Compilation Errors About Undefined Identifiers Issue Possible Cause: Missing Files Possible Cause: Unrecognized Keyword Possible Cause: Declaration Embedded in #ifdef Statements Possible Cause: Project Created from Non-Debug Build Fix Polyspace Compilation Errors About Unknown Function Prototype Issue Cause Solution Fix Polyspace Compilation Errors Related to #error Directive Issue Cause Solution Fix Polyspace Compilation Errors About Large Objects Issue Cause Solution Fix Polyspace Compilation Errors Related to Generic Compiler Issue Cause Solution Fix Polyspace Compilation Errors Related to GNU Compiler Issue Cause Solution Fix Polyspace Compilation Errors Related to Visual Compilers Import Folder pragma Pack C++/CLI Fix Polyspace Compilation Errors Related to Keil or IAR Compiler Missing Identifiers Fix Polyspace Compilation Errors Related to Diab Compiler Issue Cause Solution Fix Polyspace Compilation Errors Related to Green Hills Compiler Issue Cause Solution Fix Polyspace Compilation Errors Related to TASKING Compiler Issue Cause Solution Fix Polyspace Compilation Errors Related to Texas Instruments Compilers Issue Possible Solutions Fix Polyspace Compilation Errors About In-Class Initialization (C++) Fix Polyspace Compilation Errors About Double Declarations of Standard Template Library Functions (C++) Fix Polyspace Linking Errors About Conflicting Declarations in Different Translation Units Issue Possible Cause: Variable Declaration and Definition Mismatch Possible Cause: Function Declaration and Definition Mismatch Possible Cause: Conflicts from Unrelated Declarations Possible Cause: Macro-dependent Definitions Possible Cause: Keyword Redefined as Macro Possible Cause: Differences in Structure Packing Fix Linking Errors from Conflicts with Polyspace Header Files Issue Cause Solution Fix Polyspace Linking Errors Related to C++ Standard Template Library Stubbing Issue Cause Solution Fix Polyspace Linking Errors Related to extern "C" Blocks Extern C Functions Functional Limitations on Some Stubbed Standard ANSI Functions Fix Polyspace Compilation Errors About Namespace std Without Prefix Issue Cause Solution Fix Polyspace Compilation Warnings Related to Assertion or Memory Allocation Functions Issue Cause Solution Update Eclipse Java Version for Polyspace Plug-in Issue Cause Solution Reasons for Unchecked Code Issue Possible Cause: Compilation Errors Possible Cause: Early Red or Gray Check Possible Cause: Incorrect Options Possible Cause: main Function Does Not Terminate Identify Why Some Files or Functions are Missing in Polyspace Results Issue Possible Cause: Files Not Verified Possible Cause: Filters Applied Diagnose Why Coding Standard Violations Do Not Appear as Expected Issue Possible Cause: Rule Checker Not Enabled Possible Cause: Rule Violations in Header Files Possible Cause: Rule Violations in Macros Possible Cause: Compilation Errors Possible Cause: Code Prover Analysis with Lower Verification Level Fix Polyspace Overapproximations on Standard Library Math Functions Issue Cause Solution Fix Insufficient Memory Errors During Polyspace Report Generation Message Possible Cause Solution Fix Polyspace Errors Related to Temporary Files No Access Rights No Space Left on Device Cannot Open Temporary File Fix Errors or Slow Polyspace Runs from Disk Defragmentation and Anti-virus Software Issue Possible Cause Solution Fix SQLite I/O Errors on Running Polyspace Issue Cause Solution Fix License Error –4,0 When Running Polyspace Issue Possible Cause: Another Polyspace Instance Running Possible Cause: Prior Polyspace Run in Simulink or MATLAB Coder Fix Errors Applying Custom Annotation Format for Polyspace Results Issue Possible Solutions Troubleshooting Polyspace Access Polyspace Access ETL and Web Server services do not start Issue Possible Cause: Hyper-V Network Configuration Cannot Resolve Local Host Names Contact Technical Support About Polyspace Access Issues
Similar books
MySQL® Notes for Professionals book
2018 · PDF
MrExcel 2022: Boosting Excel
2022 · PDF
MrExcel 2022: Boosting Excel
2022 · PDF
Session C11: Ancient Cultural Landscapes in South Europe – their Ecological Setting and Evolution, Session C22: Gardeners from South America, Session S04: Agro-Pastoralism and Early Metallurgy Sessions, Session WS29: The Idea of Enclosure in Recent Iberian Prehistory, Session C88: Rhytmes et causalites des dynamiques de l'anthropisation en Europe entre 6500 ET 500 BC: Hypotheses socio-culturelles et/ou climatiques: Proceedings of the XV UISPP World Congress (Lisbon 4-9 September 2006) / Actes du XV Congrès Mondial (Lisbonne 4-9 Septembre 2006) Vol.36
2010 · PDF
THE BRITISH ARMY IN INDIA: ITS PRESERVATION BY AN APPROPRIATE CLOTHING, HOUSING, LOCATING, RECREATIVE EMPLOYMENT, AND HOPEFUL ENCOURAGEMENT OF THE TROOPS. with AN APPENDIX ON INDIA : THE CLIMATE OP ITS HILLS ; THE DEVELOPMENT OF ITS RESODRCBS, INDUSTRY, AND ARTS ; THE ADMINISTRATION OF JUSTICE ; THE BLACK ACT ; THE PROGRESS OF CHRISTIANITY ; THE TRAFFIC IN OPIUM ; THE VALUE OF INDIA ; PERMANENT CAUSES OF DISAFFECTION, AND OF THE RECENT REBELLION ; THE TRADITIONARY POLICY; MISGOVERNMENT BY NATIVE RULERS ; ANNEXATIONS OF THEIR TERRITORY, ETC.
1858 · PDF
Idries Shah 27 Books Collection : A Perfumed Scorpion, A Veiled Gazelle, Caravan of Dreams, Darkest England, Destination Mecca, Evenings with Idries Shah, Knowing How to Know, Learning How to Learn, Letters and Lectures of Idries Shah, Neglected aspects of Sufi study, Observations, Oriental Magic, Reflections, Seeker after Truth, Special Illumination, Special Problems in the study of Sufi ideas, Sufi thought and action, Tales of the Dervishes, The Dermis Probe, The Elephant in the Dark, The Englishman Handbook, Idries Shah Antology, The Magic Monastery, The natives are restless, wisdom of the Idiots PDF.
2022 · PDF
The travels of Capts. Lewis and Clarke from St. Louis, by way of the Missouri and Columbia rivers, to the Pacific ocean; performed in the years 1804, 1805 & 1806, by order of the government of the United States. Containing delineations of the manners, customs, religion, &c. of the Indians, comp. from various authentic sources, and original documents, and a summary of the Statistical view of the Indian nations, from the official communication of Meriwether Lewis. Illustrated with a map of the country, inhabited by the western tribes of Indians
1809 · PDF
Professional Linux kernel architecture ''Wrox programmer to programmer''--Cover. - ''What you are reading right now is the result of an evolution over more than seven years: After two years of writing, the first edition was published in German by Carl Hanser Verlag in 2003. It then described kernel 2.6.0. The test was used as a basis for the low-level design documentation for the EAL4+ security evaluation of Red Hat Enterprise Linux 5, requiring to update it to kernel 2.6.18 (if the EAL acronym does not mean anything to you, then Wikipedia is once more your friend). Hewlett-Packard sponsored the translation into English and has, thankfully, granted the rights to publish the result. Updates to kernel 2.6.24 were then performed specifically for this book''--P. ix
2008 · PDF