[cfe-dev] clang: Report Diagnostic ID for diagnostics

Jordan Rose jordan_rose at apple.com
Mon Oct 29 09:48:47 PDT 2012


Hi, Sujit. Our bug reports do have categories right now, which you can see in the scan-build HTML output or in Xcode. As you pointed out, though, individual bug types do not currently have IDs. This is something we've discussed internally before, but we'd like to make sure we do it right. (For example, Clang's warnings have names, not numbers. Should the analyzer also have names? Should the names be hierarchical? How should bug types correspond to whether various checkers are enabled?)

I thought there was an outstanding Bugzilla report for this, but I can't see one in a quick skim through the list. Maybe Ted or Anna can find one.

Thanks for the report,
Jordan


On Oct 28, 2012, at 21:14 , Sujit Kamthe <Sujit.Kamthe at kpitcummins.com> wrote:

> Hi,
> There is no ErrorID or StaticAnalyzerCheckerID associated with diagnostics being reported.
> e.g.
> Core.1: The right operand of '==' is a garbage value
> Security.2: < diagnostic >
> DeadCode.4: <diagnostic>
>  
> It will help categorize the diagnostics in report.
>  
> Regards,
> Sujit Kamthe
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.llvm.org/pipermail/cfe-dev/attachments/20121029/9ba6802b/attachment.html>


More information about the cfe-dev mailing list