Hey all.

I previously sent out an email regarding Coverity static analysis (see
below).

To access Coverity, one has to create an account and get accepted by one of
the Coverity project maintainers – at this point, it's Sylvestre (CC'd).
Unfortunately, I'm not sure access to Coverity is available to contributors
but Margaret suggested I forward the email to a wider audience so that
everyone is aware of where these filed bugs are coming from.

If anyone knows if Coverity is available to contributors, please let us
know!
- Mike

---------- Forwarded message ----------
From: Michael Comella <mcome...@mozilla.com>
Date: Tue, Feb 16, 2016 at 3:37 PM
Subject: Coverity static analysis


Hey all.

ahunt pointed me at Coverity, which is a static code analysis tool that can
run on our Java and C++ code. As it turns out, Sylvestre & co. had already
created a project for the mobile team and it's already live at [1] – nice
work! Additionally, it has built in support for notifications for
regressions so we can stay on top of fixing new issues.

It checks for many issues that our existing tools don't look for and only
get caught at run time, e.g. null pointer dereferences, resource leaks
(e.g. no `Cursor.close()`).

You'll need to request to become a project member in order to see the
"defects" – the button should be somewhere around the page at [1].

If you have a few free cycles, this would be a great place to start
triaging and file some bugs on Bugzilla. Even if you don't take the time to
fix the issue yourself, we can make them mentor bugs to get the ball
rolling.

I've started a meta bug [2] and triaged some of the existing issues on the
Coverity interface (they have their own – how to interface with Bugzilla?
TBD).

Let me know if you have any questions!
- Mike

[1]: https://scan.coverity.com/projects/firefox-mobile
[2]: https://bugzilla.mozilla.org/show_bug.cgi?id=1248773
_______________________________________________
mobile-firefox-dev mailing list
mobile-firefox-dev@mozilla.org
https://mail.mozilla.org/listinfo/mobile-firefox-dev

Reply via email to