dkrupp added a comment. In http://reviews.llvm.org/D12906#272243, @zaks.anna wrote:
> > > In http://reviews.llvm.org/D10305#224956, @zaks.anna wrote: > > > > > > > For example, you could keep the information about the reports in the > > > plist files and use those to > > > > > > > render the reports in HTML. > > > > > > > > > If you're okay with adding HTML file name in plist for each bug, I will > > prepare a new patch for that. > > > Thanks for the review! > > > I think you misunderstood my comment. I am not talking about using the > existing HTML files here but rather having an HTML viewer, which you could > use to browse source code. This viewer would be extended to read the bug > reports from the plist files and display them. Currently, we create an html > file with source code + report info for each bug report. This does not scale > when you have a lot of reports on a single large file (ex: sqlite). > > What I describe above is a larger project. What workflow are you trying to > support? I think adding the issue hash to the HTML file is fine if you find > it to be useful for your workflow... Hi Anna & Kim, we recognized these scalability issues you just described and that's why we created CodeChecker https://github.com/Ericsson/codechecker/ tool. A HTML report viewer for Clang SA. Reports are stored in a postgresql db. Each source file is only stored once (unlike scanbuild), supports bug suppression and diff view between runs etc. And it works pretty fast with many-million lines of code projects. If you have time, give it a try. we are happy to get feedback... Regards, Daniel http://reviews.llvm.org/D12906 _______________________________________________ cfe-commits mailing list cfe-commits@lists.llvm.org http://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits
