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.
Details
Details
Diff Detail
Diff Detail
Event Timeline
Comment Actions
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 also possible to test this with other -analyzer-output variants, but that'd be an overkill).
lib/StaticAnalyzer/Checkers/GenericTaintChecker.cpp | ||
---|---|---|
109 | Could you call this V? Because S is often a statement pointer (so often that you actually shadow this member with a local statement later). | |
681 | C.getSVal(E) Promoting the new fancy helper function^^ |
Could you call this V? Because S is often a statement pointer (so often that you actually shadow this member with a local statement later).