[MOAB-dev] coverity

[Nico Schlömer]

>  There are also several outstanding fixes in branches (valgrind_fixes,
cppcheck_fixes), which will be merged to master soon.

I set up a cronjob that submits to Coverity every Friday night such that
one can enjoy new and fixed defects from last weeks every Monday. :)
I'm curious about the results after the valgrind branch has been merged.

--Nico

On Wed, Sep 2, 2015 at 8:17 PM Vijay S. Mahadevan <vijay.m at gmail.com> wrote:

> Hi Nico,
>
> Thanks for setting up a Coverity instance for MOAB. This will be very
> useful in finding more issues in the code base.
>
> We currently do static analysis with cppcheck [1], valgrind runs for
> memory errors and test coverage with lcov [2]. There are also several
> outstanding fixes in branches (valgrind_fixes, cppcheck_fixes), which will
> be merged to master soon.
>
> I will send you a separate email once I register.
>
> Vijay
>
> [1] http://gnep.mcs.anl.gov:8010/static_analysis.html
> [2] http://gnep.mcs.anl.gov:8010/coverage.html
>
>
> On Wednesday, September 2, 2015, Nico Schlömer <nico.schloemer at gmail.com>
> wrote:
>
>> Hi everyone,
>>
>> I recently set up a Coverity instance for MOAB [1] which helps finding
>> coding errors that the compiler won't catch (resource leaks, missing
>> `break` in `switch`es and so forth).
>>
>> [image: leak.png]
>>
>> For security, not everyone can view the details of the errors, but if you
>> sign up at [1] I'll be happy to approve you.
>>
>> Cheers,
>> Nico
>>
>>
>> [1] https://scan.coverity.com/projects/moab?tab=overview
>>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.mcs.anl.gov/pipermail/moab-dev/attachments/20150903/511c29ad/attachment-0001.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: leak.png
Type: image/png
Size: 151148 bytes
Desc: not available
URL: <http://lists.mcs.anl.gov/pipermail/moab-dev/attachments/20150903/511c29ad/attachment-0001.png>