Polyspace Bug Finder Report no line number show

I saw from the generated xml file from bugfinder.rpt, the table does not indicating the line number in the source code where the defect occurs. And i run another similar report generation in code_prover with developer.rpt it does show the line number.

How i can achieve similar table as code prover report with line number?

BTW i am using r2013b matlab

Answer 1

[Anirban]

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:

• Review Polyspace Bug Finder Results in Web Browser
• Review Polyspace Code Prover Results in Web Browser

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.

[Kang Sheng Wong]

Yes. for my company process, we required to dump the every detailed of the results in archive. And with bug finder unable to export the detailed as line number in pdf/html/xml format, the reviewer have to reopen polyspace to view and verified the analysis result. And i think this is inconvenient that our company have limited license for this purpose. If every detailed in a txt file (pdf,xml/html) any user can review it more easily without the license. I hope this can be improve. Thanks for your clarification.

[Anirban]

Just to clarify, in your company process, you are required to run Bug Finder and dump all details of results, not just an overview.

Then you have multiple reviewers who will review the results from this archive. Ideally, you would like a few licenses of Bug Finder analysis engine but many licenses for review.

In R2019a, there is a solution for this. Polyspace Bug Finder Access is a viewer with a cheap enough license that you can support all your reviewers. Note that this viewer will support further investigation of a finding through code navigation shortcuts, related events, call hierarchy, and many other useful information. It is not just enough to locate an issue. One must also spend some effort in tracing the root cause of the issue (which would not be possible with an HTML/PDF report). Polyspace Bug Finder Access reduces that effort drastically.

You will find more information about this product here: https://www.mathworks.com/products/polyspace-code-prover.html

https://www.mathworks.com/products/polyspace-bug-finder.html

[Kang Sheng Wong]

Yes, for the process, we need details instead of overview. With Polyspace it is definately is easier for user to trace back the root cause, but not for archiving purpose.

And i hope the BugFinder report output has to be clearer, and has the similarity as CodeProver report output.

There are another problem in the MISRA-C-report.xml from BugFinder is unreadable, and i am unable using script to analyze the contents