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

Daniel Krupp via cfe-commits cfe-commits at lists.llvm.org
Tue Sep 22 02:02:54 PDT 2015

dkrupp added a comment.


Regarding testing:
I think we should create a RecursiveASTvistor based "test checker" that matches every statement and declaration and reports a bug there.
Then we could create a test file similar to what we have in /tools/clang/test/Analysis/diagnostics/report-issues-within-main-file.cpp
where the expected plist output can be written at the end of the file.

I am not sure though where to register this test "test checker". Should it be a dynamically loadable checker similar to /tools/clang/examples/analyzer-plugin/MainCallChecker.cpp or it should be a debug checker like (debug.DumpCalls)?

The advantage of the dynamic lib based solution is that we would not need to statically add it to clang-sa.

What do you think?



More information about the cfe-commits mailing list