[cfe-dev] Static Analysis launch checker in context of another checker

[Gábor Márton via cfe-dev]

We have the convention of modeling and reporting checkers. Modeling
checkers provide the information that is used by the reporting checkers.
Ideally, taint analysis should be implemented in this way too. So, sooner
or later we will refactor GenericTaintChecker to be like this.
Anyway, `isTainted` provided by the taint analysis is part of the modeling
and can be reused by other checkers which do some reporting. Just make sure
you register the dependency on the taint checker in Checkers.td.


On Wed, Sep 2, 2020 at 9:22 AM Thien Tran <thientc84 at gmail.com> wrote:

> Thank you very much for your response,
>
> I'm reading GenericTaintChecker and in its document "The taint information
> produced by it might be useful to other checkers". I wonder how I can get
> the information from GenericTaintChecker or is it better to add my own
> analysis to it?
>
> ----------------
> Best regards,
> Thien Tran.
>
>
> On Wed, 2 Sep 2020 at 10:06, Gábor Márton <martongabesz at gmail.com> wrote:
>
>> Hi,
>>
>> Checkers which emit bug reports are ought to be independent. So in this
>> sense, no, you cannot "launch" another checker inside the current checker.
>>
>> Hope this helps,
>> Gábor
>>
>> On Tue, 1 Sep 2020, 08:25 Thien Tran via cfe-dev, <cfe-dev at lists.llvm.org>
>> wrote:
>>
>>> Hello all,
>>>
>>> I'm writing a checker to analyze function calls in the body. Please let
>>> me know if we can launch another checker in the context of the current
>>> checker?
>>>
>>> Thank you very much!
>>>
>>> ----------------
>>> Best regards,
>>> Thien Tran.
>>> _______________________________________________
>>> cfe-dev mailing list
>>> cfe-dev at lists.llvm.org
>>> https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-dev
>>>
>>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.llvm.org/pipermail/cfe-dev/attachments/20200902/8ecdd887/attachment.html>