> -----Original Message-----
> From: dev [mailto:dev-bounces at dpdk.org] On Behalf Of Thomas Monjalon
> Sent: Friday, March 20, 2015 2:51 PM
> To: dev at dpdk.org
> Subject: [dpdk-dev] tools brainstorming
> 
> As we are lazy developers, writing guidelines is not enough. It must be
> coupled with the integration of some tools. Let's work on these ones:
>       - make autotests easier and faster to run for smoke testing
>       - automated basic testpmd check
>       - build check with various options combinations
>       - abi check (started with validate-abi.sh)
>       - static analyze (clang, free online coverity)


Hi,

There was a discussion about using Coverity several months ago and Vincent set 
up an initial project.

    http://dpdk.org/ml/archives/dev/2014-August/004962.html

I created a similar Coverity project and have been uploading snapshots since 
January and comparing the results to a similar tool we use internally (it 
compares well). 

If anyone would like to view the analysis results you can sign up to Coverity 
and apply for access to the DPDK project. 

    https://scan.coverity.com/users/sign_up
    https://scan.coverity.com/projects/4005 (DPDK)

Alternatively, drop me an email and I'll send you an invite. Apply as 
Contributor/Member if you plan to review/close issues or as Defect Viewer if 
you just wish to see the issues.

Like any static analysis tool there may be false positives. These can be 
flagged as such.

John
-- 

Reply via email to