Re: Postgresql and Clang Static Analyzer

From: "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com>
To: Дилян Палаузов <dpa-postgres(at)aegee(dot)org>
Cc: "pgsql-bugs(at)postgresql(dot)org" <pgsql-bugs(at)postgresql(dot)org>
Subject: Re: Postgresql and Clang Static Analyzer
Date: 2017-05-05 21:40:11
Message-ID: CAKFQuwZgxhbs1y7FC3UG1r+FRUNDf8bdVMZCPCwK2adGKc89uQ@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

On Fri, May 5, 2017 at 2:36 PM, Дилян Палаузов <dpa-postgres(at)aegee(dot)org>
wrote:

> Hello,
>
> I compiled postgresql with
>
> PYTHON=/usr/local/bin/python3 scan-build ./configure --with-perl
> --with-tcl --with-gssapi --with-ldap --with-openssl --with-libxml
> --with-libxslt --with-systemd --with-python
>
> scan-build make
>
> and here are the results:
> https://mail.aegee.org/dpa/scan-build-pg-b3a47cdfd6/
>
>
> Please note, that the information is only about what gets actually
> compiled, code disabled by #if .. #endif is not considered (e.g. when
> determining whether a variable assignment is useless). There are probably
> some false-positives.
>
> I used scan-build/clang 4.0.
>
> Enjoy

​We much prefer if emails to bugs are self-contained and not pointing to
some random web URL which cautious people aren't going to follow. It would
also be helpful to actually state in your own words what you believe the
bug is/what the correct behavior should be.

​David J.

In response to

Browse pgsql-bugs by date

  From Date Subject
Next Message Bill Parker 2017-05-05 21:41:00 Re: Postgresql and Clang Static Analyzer
Previous Message Дилян Палаузов 2017-05-05 21:36:13 Postgresql and Clang Static Analyzer