Main Content
Interpret Bug Finder Results
Interpret Bug Finder result message and navigate source code to
find root cause of result
Learn how to use the different panes of the Polyspace® Bug Finder™ user interface to review analysis results and find the root cause of a defect.
Topics
Getting Started
- Interpret Bug Finder Results in Polyspace Desktop User Interface
Interpret result details message, find root cause of result. - Investigate the Cause of Empty Results List
Learn what procedure to follow if the Results List pane is empty.
Understanding Bug Finder Results
- Polyspace Results in Lines Containing Macros
See how Polyspace shows results in source code lines containing macros. - Understanding Changes in Polyspace Results After Product Upgrade
Compare results before and after upgrade, interpret differences based on release notes and general direction of trends in Code Prover releases. - Bug Finder Analysis Assumptions
Assumptions used during code analysis
Polyspace User Interface
- Dashboard in Polyspace Desktop User Interface
The Dashboard pane shows an overview of Bug Finder results in graphical format, for instance, defect distribution by impact. - Concurrency Modeling in Polyspace Desktop User Interface
The Concurrency Modeling pane shows the entry point functions in a multitasking application, and whether they are detected automatically from the code or explicitly specified. - Results List in Polyspace Desktop User Interface
The Results List pane lists Bug Finder results with attributes such as file, function and review status. - Source Code in Polyspace Desktop User Interface
The Source pane shows source code overlaid with Bug Finder results. - Result Details in Polyspace Desktop User Interface
The Result Details pane shows details of a specific Bug Finder result along with review information. - Call Hierarchy in Polyspace Desktop User Interface
The Call Hierarchy pane shows callers and callees of a function.