New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Coverity Scan results #1500
Comments
cc #1499 |
We could also run the scan on each Travis build, there's an interface for that. |
Just uploaded a new scan and we have 198 new defects but I think that's because analysis were not run to completion previously or something since it's all in old code. |
Total defects count is around 1970. |
How severe are these?
|
It depends, a big part of these are memory leaks which take up memory but do not make the program crash. I'm trying to fix double frees right now because these can be hard to debug sometimes. There isn't too much of them. |
I am proposing to close this because we have a lot of these, [some should be closed, others are unnecessary] (⇐ generally speaking I mean) and they should be triaged properly from the dashboard whatsoever. |
The Coverity Scan dashboard? I think its ok to leave this open, someone else might appear and want to work on this :) |
I think the Coverity scanning can be a very good thing, even when it can get defects wrong. And we do need a place to talk about specific items and/or strategies. First two line items I looked at today, the first is a leak, and the second isn't but the false positive can be worked around as two different variables were being juggled which confused the scanner. Then I peeked at a third line item:
Uninitialized variable... well blaaahh, ya'know? (hmm, no tests test AddHHint or AddVHint - how to easily do a test? Blaahh!) |
@tshinnic Can you submit a Pull Request for it? |
Done. #1655 with bonus double-free fix! |
There's a database of these. |
Please find the latest report on new defect(s) introduced to FontForge found with Coverity Scan. Showing 20 of 1970 defect(s)
The text was updated successfully, but these errors were encountered: