The Bug Finder reports are meant for archiving purposes only (to maintain snapshots of the code quality at specific milestones). To see exact locations of Polyspace Bug Finder results in the code, you have to open the results in the Polyspace GUI (or in the Eclipse plugin if you are using Eclipse).
Since R2019a, the new product Polyspace Access allow teams to look at common results hosted on a server, using a web browser only. If you were using HTML/Word/PDF reports to share results with others, you can switch to the new product for a more convenient workflow. See here for details:
In both the Polyspace GUI or the new Polyspace Access web interface, you have support from features such as code navigation shortcuts, event history, tooltips, function call sequence leading to defect, and other such tools to better understand why a defect or rule violation can happen. The HTML reports with only the results themselves do not provide these conveniences.
If you are using one of these products to run your analysis:
- Polyspace Bug Finder Server
- Polyspace Code Prover Server
And need to see line numbers in your reports, please contact your MathWorks representative.