On Tue, Jan 13, 2015 at 10:56 AM, Peter Meerwald <pmeerw at pmeerw.net> wrote: > >> >> User maksqwe on Russian website habrahabr checked pulseuadio sources >> >> with PVS Studio static analyzer and found a few issues. I additionaly >> >> checked it with Cppcheck analyzer. Fixes follows. >> >> >> >> There are more issues, I try to make fixes for them too shortly. >> > >> > applied, thanks >> >> Coverity might be a good idea as well. Maybe a new run should be done >> on that as well? The last one is from march 2014. >> >> Note that coverity runs can be semi-automated via travis-ci, so it >> becomes easier to run (just push to a coverity_scan branch). >> >> I could help in setting up travis and coverity for pa. > > at the moment there are (too) many false positives, I fixed some obvious > issues bug but many are left > > maybe a more automated scan would be good nevertheless; it any hosting > setup necessary? For automated scans, one needs to sign up to travis-ci, and then designate a branch for coverity scans (in order to rate-limit the scans). Then any time you push to that branch, travis will run coverity on the code. So, other than setting up a post-upload hook on the git server, nothing needs to be done. -- Saludos, Felipe Sateler
