From: "Piotr Dałek" <branch@predictor.org.pl>
To: Brad Hubbard <bhubbard@redhat.com>
Cc: ceph-devel@vger.kernel.org
Subject: Re: Static analysis
Date: Wed, 23 Nov 2016 08:25:24 +0100 [thread overview]
Message-ID: <20161123072524.GE26997@predictor> (raw)
In-Reply-To: <20161123070637.GF26846@rskikr.localdomain>
On Wed, Nov 23, 2016 at 05:06:37PM +1000, Brad Hubbard wrote:
> I did a run of the Clang Static Analyzer and it turned up multiple issues which
> Kefu gobbled up :) The reports are quite detailed and walk you through how the
> issue can present.
>
> See https://github.com/ceph/ceph/pull/12145 and
> https://github.com/ceph/ceph/pull/12148
>
> Given how easy it is to run [1] (although slow) would it be a good idea to be
> running this regulary, perhaps in addition to coverity scans?
>
> [1] mkdir build && cd build && scan-build cmake .. && scan-build make -jX
+1. Certainly this will help finding out obscure bugs that show up later in
unexpected places.
--
Piotr Dałek
branch@predictor.org.pl
http://blog.predictor.org.pl
next prev parent reply other threads:[~2016-11-23 7:32 UTC|newest]
Thread overview: 53+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-23 7:06 Static analysis Brad Hubbard
2016-11-23 7:25 ` Piotr Dałek [this message]
2016-11-23 14:23 ` Sage Weil
-- strict thread matches above, loose matches on Subject: below --
2016-12-23 9:20 Brad Hubbard
2016-12-31 0:22 Brad Hubbard
2017-01-10 2:29 Static Analysis Brad Hubbard
2017-01-17 1:32 Brad Hubbard
2017-03-03 5:11 Brad Hubbard
2017-03-10 5:50 Brad Hubbard
2017-03-25 23:54 Brad Hubbard
2017-03-31 1:33 Brad Hubbard
2017-04-07 0:31 Brad Hubbard
2017-04-14 1:04 Brad Hubbard
2017-04-14 11:48 ` kefu chai
2017-04-21 4:37 Brad Hubbard
2017-04-28 2:33 Brad Hubbard
2017-05-05 22:20 Brad Hubbard
2017-05-14 23:44 Brad Hubbard
2017-05-19 2:37 Brad Hubbard
2017-06-02 6:43 Brad Hubbard
2017-06-13 1:41 Brad Hubbard
2017-06-16 7:38 Brad Hubbard
2017-06-22 9:23 Brad Hubbard
2017-06-29 9:15 Brad Hubbard
2017-07-06 6:18 Brad Hubbard
2017-07-13 10:22 Brad Hubbard
2017-07-20 7:36 Brad Hubbard
2017-07-28 0:49 Brad Hubbard
2017-08-03 7:30 Brad Hubbard
2017-08-10 6:58 Brad Hubbard
2017-08-18 1:55 Brad Hubbard
2017-08-28 4:33 Brad Hubbard
2017-08-31 7:19 Brad Hubbard
2017-09-08 3:14 Brad Hubbard
2017-09-14 9:09 Brad Hubbard
2017-09-21 4:31 Brad Hubbard
2017-09-22 23:44 Static analysis Mat Martineau
2017-09-28 4:00 Static Analysis Brad Hubbard
2017-10-05 0:00 Brad Hubbard
2017-10-12 1:34 Brad Hubbard
2017-10-19 3:58 Brad Hubbard
2017-10-27 2:19 Brad Hubbard
2017-11-02 1:05 Brad Hubbard
2017-11-09 22:51 Brad Hubbard
2017-11-16 22:58 Brad Hubbard
2017-11-23 3:38 Brad Hubbard
2017-12-01 2:50 Brad Hubbard
2017-12-08 0:47 Brad Hubbard
2017-12-14 8:35 Brad Hubbard
2017-12-20 23:54 Brad Hubbard
2017-12-28 0:11 Brad Hubbard
2018-01-04 8:38 Brad Hubbard
2018-01-18 4:10 Brad Hubbard
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=20161123072524.GE26997@predictor \
--to=branch@predictor.org.pl \
--cc=bhubbard@redhat.com \
--cc=ceph-devel@vger.kernel.org \
/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.