From: chrubis@suse.cz
To: Jan Stancek <jstancek@redhat.com>
Cc: LTP List <ltp-list@lists.sourceforge.net>
Subject: Re: [LTP] Coverity report for ltp-20130109
Date: Tue, 19 Mar 2013 18:43:52 +0100 [thread overview]
Message-ID: <20130319174351.GA1678@rei> (raw)
In-Reply-To: <623806259.21081036.1363706313082.JavaMail.root@redhat.com>
Hi!
> 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've looked at the results briefly and allready found and fixed one
(quite stupid) bug in doio.c.
But there seems to be quite a number of false possitives because LTP
does things that are usually wrong intentionally (i.e. NULL
dereference). We could probably mask most of the cases from the compiler
by setting such variables as volatile, but I'm not really sure if it's
worth of it.
--
Cyril Hrubis
chrubis@suse.cz
------------------------------------------------------------------------------
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
prev parent reply other threads:[~2013-03-19 17:43 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 ` [LTP] Coverity report for ltp-20130109 Jan Stancek
2013-03-19 15:28 ` 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 [this message]
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=20130319174351.GA1678@rei \
--to=chrubis@suse.cz \
--cc=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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox