From: Jeff King <peff@peff.net>
To: Tomas Carnecky <tom@dbservice.com>
Cc: git list <git@vger.kernel.org>
Subject: Re: clang static analyzer
Date: Sun, 6 Dec 2009 09:57:44 -0500 [thread overview]
Message-ID: <20091206145744.GA6725@coredump.intra.peff.net> (raw)
In-Reply-To: <33ABC714-2BCC-4910-BCAE-D331AAF2A724@dbservice.com>
On Sun, Dec 06, 2009 at 07:11:24AM +0100, Tomas Carnecky wrote:
> Clang again found many dead assignments/increments, but in the earlier
> discussions you concluded that you want to keep those around. So I
> focussed on another class of potential bugs: Argument with 'nonnull'
> attribute passed null. There were a total of seven such issues. I then
> tried to look through the code and see if they are valid or false
> positives:
Thanks, I think you are moving in the right direction to manually
investigate the output of clang, since it obviously does generate some
false positives.
I think the next step for each site you found would be:
1. If it really is a problem, then it should be easy to show a simple
case that can trigger the issue. Submit a patch fixing that site,
either describing the test case in the commit message, or adding a
case to the test suite.
2. If it is a false positive, see what it would take to silence clang
and submit a patch. I don't think we are opposed to annotations
that help analysis tools as long as those annotations aren't too
intrusive or make the code less readable.
-Peff
next prev parent reply other threads:[~2009-12-06 14:57 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-06 6:11 clang static analyzer Tomas Carnecky
2009-12-06 14:57 ` Jeff King [this message]
2009-12-06 15:39 ` Nicolas Pitre
2009-12-06 16:04 ` Jeff King
2009-12-06 23:49 ` Nicolas Sebrecht
2009-12-07 0:18 ` Junio C Hamano
2009-12-07 0:26 ` Junio C Hamano
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=20091206145744.GA6725@coredump.intra.peff.net \
--to=peff@peff.net \
--cc=git@vger.kernel.org \
--cc=tom@dbservice.com \
/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