public inbox for ltp@lists.linux.it
 help / color / mirror / Atom feed
From: Jan Stancek <jstancek@redhat.com>
To: ltp-list <ltp-list@lists.sf.net>
Subject: Re: [LTP] Coverity report for ltp-20150420
Date: Thu, 30 Apr 2015 04:22:01 -0400 (EDT)	[thread overview]
Message-ID: <162165083.8714320.1430382121729.JavaMail.zimbra@redhat.com> (raw)
In-Reply-To: <782230467.5857849.1429883677704.JavaMail.zimbra@redhat.com>





----- Original Message -----
> From: "Jan Stancek" <jstancek@redhat.com>
> To: "ltp-list" <ltp-list@lists.sf.net>
> Sent: Friday, 24 April, 2015 3:54:37 PM
> Subject: [LTP] Coverity report for ltp-20150420
> 
> Hi,
> 
> What is Coverity?
>   Coverity Prevent is commercial enterprise level tool for static analysis
>   (analysis based only on compiling of sources, not based on running of
>   binary)
>   of the C/C++ and Java code.
> analyzer-version-coverity = 7.6.1
> 
> This run includes latest LTP release 20150420 (including
> open_posix_testsuite):
>   http://jan.stancek.eu/coverity/ltp-20150420.err.xz
> 
>       1 ARRAY_VS_SINGLETON
>       4 BAD_COMPARE
>      17 BAD_FREE

I went through most of BAD_FREE reports yesterday and in many cases it was
mmap + munmap with some offset, which coverity doesn't like.

From what I have read, it should be possible to annotate code to make coverity
stop complaining. For example by adding following:
  /* coverity[EVENT_TAG_NAME] */

I'm not exactly clear where to get "event tag names" yet, as these seem to be
different from error names that appear in *.err logs.

Before I dig deeper into this, would anyone be opposed if we start adding
such annotation to LTP source?

Regards,
Jan


>       1 CHAR_IO
>     319 CHECKED_RETURN
>       6 CONSTANT_EXPRESSION_RESULT
>       3 COPY_PASTE_ERROR
>      29 DEADCODE
>       1 EVALUATION_ORDER
>      43 FORWARD_NULL
>       3 IDENTICAL_BRANCHES
>      21 MISSING_BREAK
>     497 NEGATIVE_RETURNS
>       7 NO_EFFECT
>       6 NULL_RETURNS
>       1 OVERFLOW_BEFORE_WIDEN
>      27 OVERRUN
>       1 PASS_BY_VALUE
>     343 RESOURCE_LEAK
>       1 RETURN_LOCAL
>       1 REVERSE_INULL
>       2 REVERSE_NEGATIVE
>      19 SIZEOF_MISMATCH
>       1 STRAY_SEMICOLON
>      91 UNINIT
>      14 UNREACHABLE
>       6 UNUSED_VALUE
>      48 USE_AFTER_FREE
>       1 VARARGS
> 
> Regards,
> Jan
> 
> ------------------------------------------------------------------------------
> One dashboard for servers and applications across Physical-Virtual-Cloud
> Widest out-of-the-box monitoring support with 50+ applications
> Performance metrics, stats and reports that give you Actionable Insights
> Deep dive visibility with transaction tracing using APM Insight.
> http://ad.doubleclick.net/ddm/clk/290420510;117567292;y
> _______________________________________________
> Ltp-list mailing list
> Ltp-list@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/ltp-list
> 

------------------------------------------------------------------------------
One dashboard for servers and applications across Physical-Virtual-Cloud 
Widest out-of-the-box monitoring support with 50+ applications
Performance metrics, stats and reports that give you Actionable Insights
Deep dive visibility with transaction tracing using APM Insight.
http://ad.doubleclick.net/ddm/clk/290420510;117567292;y
_______________________________________________
Ltp-list mailing list
Ltp-list@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/ltp-list

  parent reply	other threads:[~2015-04-30  8:22 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1555406842.5673672.1429863249724.JavaMail.zimbra@redhat.com>
2015-04-24 13:54 ` [LTP] Coverity report for ltp-20150420 Jan Stancek
2015-04-27 13:24   ` Cyril Hrubis
     [not found]     ` <699964060.6783089.1430144771050.JavaMail.zimbra@redhat.com>
2015-04-27 15:58       ` Cyril Hrubis
     [not found]         ` <1789445018.7218822.1430210865329.JavaMail.zimbra@redhat.com>
2015-04-28  9:47           ` Cyril Hrubis
2015-04-30  8:22   ` Jan Stancek [this message]
2015-04-30  9:03     ` Cyril Hrubis

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=162165083.8714320.1430382121729.JavaMail.zimbra@redhat.com \
    --to=jstancek@redhat.com \
    --cc=ltp-list@lists.sf.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox