On Tue, Jan 3, 2017 at 4:44 PM, Brad Hubbard <bhubbard@xxxxxxxxxx> wrote: > > > On Wed, Jan 4, 2017 at 10:30 AM, Gregory Farnum <gfarnum@xxxxxxxxxx> wrote: >> On Sun, Dec 18, 2016 at 6:45 PM, Brad Hubbard <bhubbard@xxxxxxxxxx> wrote: >>> As you would have noticed in recent weeks we have returned to running a >>> Coverity test over the source tree on a weekly basis. In addition, I have been >>> running Clang Static Analyzer and Cppcheck scans. Until we can find a better >>> home for these and include at least one of them in our CI processes I will be >>> hosting them at http://people.redhat.com/bhubbard/ >> >> So...is there some way for people to feed back into that as we >> evaluate stuff? For instance I looked at one of the use-after-free >> reports[1] and it's incorrect and I think there's a way to tell >> Coverity so, but I've no idea how. >> -Greg >> >> [1]: http://people.redhat.com/bhubbard/scan-build.16-12-30/report-46bfed.html#EndPath > > Hi Greg, > > That report is from Clang Static Analyzer (not Coverity) and I am happy to > coordinate feedback as best I can for now. D'oh, I was just substituting that everywhere in my head for some reason. :o Sorry and thanks. > > There is a FAQ here, http://clang-analyzer.llvm.org/faq.html > >>> >>> -- >>> Cheers, >>> Brad >>> -- >>> To unsubscribe from this list: send the line "unsubscribe ceph-devel" in >>> the body of a message to majordomo@xxxxxxxxxxxxxxx >>> More majordomo info at http://vger.kernel.org/majordomo-info.html > > > > -- > Cheers, > Brad -- To unsubscribe from this list: send the line "unsubscribe ceph-devel" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
