Manna added a comment.
In D150744#4350048 <https://reviews.llvm.org/D150744#4350048>, @steakhal wrote:
>
> In our case, we initialized that field from the registration function, like
> this:
>
> void ento::registerMoveChecker(CheckerManager &mgr) {
> MoveChecker *chk = mgr.registerChecker<MoveChecker>();
> chk->setAggressiveness(
> mgr.getAnalyzerOptions().getCheckerStringOption(chk, "WarnOn"), mgr);
> // <--- initialized here
> }
Yes, While investigating other Coverity bugs about uninitialized scaler fields
in StaticAnalyzer, i noticed about the registration function.
CHANGES SINCE LAST ACTION
https://reviews.llvm.org/D150744/new/
https://reviews.llvm.org/D150744
_______________________________________________
cfe-commits mailing list
cfe-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits
