| Summary: | ASTERISK-26651: Using static analyze in Asterisk | ||
| Reporter: | Badalian Vyacheslav (slavon) | Labels: | |
| Date Opened: | 2016-12-08 10:06:15.000-0600 | Date Closed: | 2020-01-14 11:21:07.000-0600 |
| Priority: | Major | Regression? | |
| Status: | Closed/Complete | Components: | |
| Versions: | GIT | Frequency of Occurrence | |
| Related Issues: | |||
| Environment: | Attachments: | ||
| Description: | Unfortunately the frequent changes in the project led to a large Number of bugs. We use PVS-Studio (and some others to) as one of the best of static code analyzers. Its an advantage that it is not obvious errors, such as typos and violations of logic.
I am not an employee of the company and do not have to do with them. I just want that the quality of your project finally improved. They have recently opened their system to open source projects. Sample analysis Aasterisk project in 2014 (since then the system has greatly improved) http://www.viva64.com/en/m/0036/ I beg to introduce this (or better, and others) analyzers in continuous build system. Example of usage in CI and linux: http://www.viva64.com/en/m/0036/ How to use for free in Asterisk and other opensource projects: http://www.viva64.com/en/b/0457/ Auto create comments for free use: https://github.com/viva64/how-to-use-pvs-studio-free | ||
| Comments: | By: Asterisk Team (asteriskteam) 2016-12-08 10:06:16.609-0600 Thanks for creating a report! The issue has entered the triage process. That means the issue will wait in this status until a Bug Marshal has an opportunity to review the issue. Once the issue has been reviewed you will receive comments regarding the next steps towards resolution. A good first step is for you to review the [Asterisk Issue Guidelines|https://wiki.asterisk.org/wiki/display/AST/Asterisk+Issue+Guidelines] if you haven't already. The guidelines detail what is expected from an Asterisk issue report. Then, if you are submitting a patch, please review the [Patch Contribution Process|https://wiki.asterisk.org/wiki/display/AST/Patch+Contribution+Process]. By: Asterisk Team (asteriskteam) 2016-12-08 10:06:16.972-0600 We appreciate the difficulties you are facing, however information request type issues would be better served in a different forum. The Asterisk community provides support over IRC, mailing lists, and forums as described at http://asterisk.org/community. The Asterisk issue tracker is used specifically to track issues concerning bugs and documentation errors. If this issue is actually a bug please use the Bug issue type instead. Please see the Asterisk Issue Guidelines [1] for instruction on the intended use of the Asterisk issue tracker. Thanks! [1] https://wiki.asterisk.org/wiki/display/AST/Asterisk+Issue+Guidelines | ||