Interpréter les résultats Bug Finder
Interpréter le message de résultat Bug Finder et explorer le code source pour identifier la cause première du résultat.
Découvrez comment utiliser les différents volets de l’interface utilisateur Polyspace® Bug Finder™ pour examiner les résultats de l’analyse et identifier la cause première d’un défaut.
Rubriques
Pour commencer
- 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.
Comprendre les résultats Bug Finder
- 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. - Hypothèses d’analyse Bug Finder
Hypothèses utilisées lors de l'analyse du code
Interface utilisateur Polyspace
- 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.
