From: | Stefan Kaltenbrunner <stefan(at)kaltenbrunner(dot)cc> |
---|---|
To: | Alexander Korotkov <aekorotkov(at)gmail(dot)com>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: Happy new year from viva64 |
Date: | 2013-12-27 16:43:13 |
Message-ID: | 52BDAE21.8030005@kaltenbrunner.cc |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On 12/27/2013 01:27 PM, Alexander Korotkov wrote:
> Hackers,
>
> I believe many of us have seen report of checking PostgreSQL with
> PVS-Studio.
> http://www.viva64.com/en/b/0227/
> Me and Oleg Bartunov got license key for PVS-Studio. Thanks Viva64 for it.
> I've just run PVS-Studio against PostgreSQL head and it gives me very
> many warnings. CSV-file with them is attached. I believe most of them
> are just noise. But there could be useful warning which aren't mentioned
> in the blog post.
> Probably somebody have ideas about what to do this that list?
hmm reading up on the generated warnings I wonder if that list was
generated with the default/recommended settings of the static analyzer -
for example there is a _ton_ of V122 - "Memsize type is used in the
struct/class." errors but the docs on http://www.viva64.com/en/d/0070/
state:
"By default it is disabled since it generates false warnings in more
than 99% of cases."
So maybe you need to apply some default settings to get a more sensible
report to start from?
Stefan
From | Date | Subject | |
---|---|---|---|
Next Message | Alvaro Herrera | 2013-12-27 17:39:21 | truncating pg_multixact/members |
Previous Message | Christian Convey | 2013-12-27 16:14:17 | Re: Question about Lockhart's book |