This revision was automatically updated to reflect the committed changes.
Closed by commit rL297324: [analyzer] Add bug visitor for taint checker.
(authored by zaks).
Changed prior to commit:
https://reviews.llvm.org/D30289?vs=89497&id=91102#toc
Repository:
rL LLVM
https://reviews.llvm.org/
zaks.anna accepted this revision.
zaks.anna added a comment.
This revision is now accepted and ready to land.
Looks great!
https://reviews.llvm.org/D30289
___
cfe-commits mailing list
cfe-commits@lists.llvm.org
http://lists.llvm.org/cgi-bin/mailman/
vlad.tsyrklevich updated this revision to Diff 89497.
vlad.tsyrklevich marked 2 inline comments as done.
vlad.tsyrklevich added a comment.
Fixes and a test for Artem's suggestions.
https://reviews.llvm.org/D30289
Files:
lib/StaticAnalyzer/Checkers/GenericTaintChecker.cpp
test/Analysis/taint
NoQ added a comment.
Yay, this is awesome!
It's actually possible to test visitors with the `-analyzer-output=text`
option. This option converts path notes to `note:` diagnostics, which you can
catch with `expected-note{{}}`, see `test/Analysis/inlining/path-notes.c` for
an example (well, it's
vlad.tsyrklevich created this revision.
Add a bug visitor to the taint checker to make it easy to distinguish where the
tainted value originated. This is especially useful when the original taint
source is obscured by complex data flow.
https://reviews.llvm.org/D30289
Files:
lib/StaticAnaly
