From: Jan Stancek <jstancek@redhat.com>
To: LTP List <ltp-list@lists.sourceforge.net>
Subject: [LTP] Coverity report for ltp-20130109
Date: Tue, 19 Mar 2013 11:18:33 -0400 (EDT) [thread overview]
Message-ID: <623806259.21081036.1363706313082.JavaMail.root@redhat.com> (raw)
In-Reply-To: <1437086244.21063924.1363705319128.JavaMail.root@redhat.com>
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 coverity
analyzer-args --wait-for-license -co BAD_FREE:allow_first_field:true --all
analyzer-version Coverity Static Analysis for C/C++ version 6.5.1 on Linux 2.6.32-279.el6.x86_64 x86_64
I ran it for current LTP stable (20130109) (on top of RHEL6.4)
and I'm sharing results here:
http://jan.stancek.eu/coverity/ltp-20130109-1.el6.err.xz
I looked at results only very briefly so far. The one that caught my
eye was actually my previous email: inode02: fix "slash" array overrun.
This run includes "--all" parameter, so it's likely there are some false
positives.
Regards,
Jan
------------------------------------------------------------------------------
Everyone hates slow websites. So do we.
Make your web apps faster with AppDynamics
Download AppDynamics Lite for free today:
http://p.sf.net/sfu/appdyn_d2d_mar
_______________________________________________
Ltp-list mailing list
Ltp-list@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/ltp-list
next parent reply other threads:[~2013-03-19 15:18 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1437086244.21063924.1363705319128.JavaMail.root@redhat.com>
2013-03-19 15:18 ` Jan Stancek [this message]
2013-03-19 15:28 ` [LTP] Coverity report for ltp-20130109 chrubis
2013-03-19 16:09 ` chrubis
[not found] ` <1590001509.21115132.1363709682126.JavaMail.root@redhat.com>
2013-03-19 16:38 ` chrubis
2013-03-19 17:43 ` chrubis
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=623806259.21081036.1363706313082.JavaMail.root@redhat.com \
--to=jstancek@redhat.com \
--cc=ltp-list@lists.sourceforge.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.