3 ms·
If it's anything like the Neovim coverity report, it's probably not particularly interesting. But it is extremely helpful, and it's impressive what static analy
by justinmk 12y ago
If it's anything like the Neovim coverity report, it's probably not particularly interesting. But it is extremely helpful, and it's impressive what static analysis can find in a legacy C codebase. Here's the Neovim clang analysis:
http://neovim.org/doc/build-reports/clang/ http://neovim.org/doc/build-reports/clang/
Click on any of the "View Report" links to see a line-by-line step-through of each suspected bug.
(Coverity doesn't allow public access to reports AFAIK, so can't link to it.)
- seren 12y agoSorry to highjack the thread, but if I want to fix some neovim Coverity issues, where should I register / who should I ask ? I have already had a look to your waffle but it was not crystal clear. Just creating a Coverity account will allow me to access the report ? Thanks in advance.
- davis 12y agoLogin then go to https://scan.coverity.com/projects/2227 https://scan.coverity.com/projects/2227 and request access. If you want to fix Coverity issues, request access at the Contributor level. For more info on Coverity fixes and conventions, check out the Wiki page: https://github.com/neovim/neovim/wiki/Contributing#coverity https://github.com/neovim/neovim/wiki/Contributing#coverity