[PATCH] D10305: [Clang Static Analyzer] Bug identification

Honggyu Kim via cfe-commits cfe-commits at lists.llvm.org
Mon Sep 7 06:39:05 PDT 2015


honggyu.kim added a comment.

Sorry for the late answer.
I would like to write the comment for HTML report comparison first.

> > As I mentioned, I think the simplist way of comparing HTML reports is to have the BugID in each HTML report so that we can just compare HTML reports >whether the file exists or not.

> 

> 

> I believe scan-build creates and names those files. How do you propose to pass this information from the clang invocation to scan-build? Can you check if the BugID is already part of the HTML report itself? That might be a much simpler solution.


I meant that having BugID in the file name of HTML report would be beneficial when it comes to comparison. For example, report-<BugID_1234>.html and report-<BugID_1234>.html can be easily compared by their file names without observing the inside.

As you mentioned, there is a way to generate HTML report that has such file name with "-analyzer-config stable-report-filename=true" option. It is described in scan-build help message:

  -analyzer-config <options>
  
    Provide options to pass through to the analyzer's -analyzer-config flag.
    Several options are separated with comma: 'key1=val1,key2=val2'
  
    Available options:
      * stable-report-filename=true or false (default)
        Switch the page naming to:
        report-<filename>-<function/method name>-<id>.html
        instead of report-XXXXXX.html

It seems that I can easily compare the result with HTML file names with this option.


http://reviews.llvm.org/D10305





More information about the cfe-commits mailing list