It would be great to have a [Coverity] configured for the project so the
security of the code is checked in an automated way periodically. Coverity is a
strong tool using static analysis to reveal potential problems with the code
(e.g., buffer overflows, double free, ...)
Travis is already configured for OpenSIPS so adding it to the Coverity would be
quite easy. I would do that, but only repository administrators can do it.
I have configured Coverity scanning on my [fork] of the OpenSIPS. Take a look
if interested. It took 5 minutes to configure it. Here is the Coverity report:
https://scan.coverity.com/projects/ph4r05-opensips?tab=overview
[Coverity]: https://scan.coverity.com/
[fork]: https://github.com/ph4r05/opensips/tree/coverity_scan
---
Reply to this email directly or view it on GitHub:
https://github.com/OpenSIPS/opensips/issues/713
_______________________________________________
Devel mailing list
[email protected]
http://lists.opensips.org/cgi-bin/mailman/listinfo/devel
