search

javigon / vim

Automatically exported from code.google.com/p/vim
0 stars 0 forks source link

Coverity Static Code Analysis Resutls #333

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago 
The attached document are high sightings found by a Coverity scan ran today for 
Vim 7.4.  Some of these may be false positives, but it may be good for others 
to take a look.

Original issue reported on code.google.com by john.l.w...@intel.com on 19 Feb 2015 at 10:58

Attachments:

GoogleCodeExporter commented 9 years ago 
Thanks! What patch level is this? Or is it 7.4.0? Is that all of them or did 
you share just a selection?

Note, there is a cov-format-errors command that can generate an error list 
usable by vim's quickfix. I wrote a compiler plugin that sets an appropriate 
errorformat: http://www.vim.org/scripts/script.php?script_id=3936

For some items you've provided only the screenshot of the final problem, but 
not the logic needed to reach that problem spot, which I've found to be a 
useful part of the Coverity results. That same cov-format-errors command can 
provide an HTML dump that mirrors what you'd see in the Coverity server. I 
think the info in this is equivalent to that in the error list but I'm not 
certain on that.

Perhaps the error list or html dump would be useful to address some of these.

Original comment by fritzoph...@gmail.com on 20 Feb 2015 at 2:41

GoogleCodeExporter commented 9 years ago 
Although I appreciate reporting possible issues, it's a lot easier to deal with 
them by creating a separate issue for every problem.  Please split it up, so 
that we can mark each issue with specific comments and close the ones that get 
fixed.

Original comment by brammool...@gmail.com on 20 Feb 2015 at 6:48

GoogleCodeExporter commented 9 years ago 
Ok, sounds good.  I recommend closing this one then and I can go back and 
dispatch each applicable issue in a better format per fritzophrenic's comments. 
 Thanks!

Original comment by john.l.w...@intel.com on 20 Feb 2015 at 11:00

GoogleCodeExporter commented 9 years ago 
Okay, closing as invalid then. Feel free to open new issues for individual 
issues. This allows for easier tracking the problems.

Original comment by chrisbr...@googlemail.com on 25 Feb 2015 at 9:32