Re: [BUGS] Postgresql and Clang Static Analyzer
| От | Bill Parker |
|---|---|
| Тема | Re: [BUGS] Postgresql and Clang Static Analyzer |
| Дата | |
| Msg-id | CAFrbyQxs0kE26qBydVChNAe+2fi6=sBv8O_LfsCNmbzmgZMxcg@mail.gmail.com обсуждение исходный текст |
| Ответ на | [BUGS] Postgresql and Clang Static Analyzer (Дилян Палаузов<dpa-postgres@aegee.org>) |
| Ответы |
Re: [BUGS] Postgresql and Clang Static Analyzer
|
| Список | pgsql-bugs |
This by itself doesn't prove the existence of a bug, while it's a useful tool to find pieces of code which MIGHT be a problem, it doesn't prove that every instance is an actual bug :)
Clang-Analyzer and other static analysis tools are useful when used with actually reading the code in question (I've found bugs which clang-analyzer has actually missed in other software projects)
On Fri, May 5, 2017 at 2:36 PM, Дилян Палаузов <dpa-postgres@aegee.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
Дилян
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-bugs
В списке pgsql-bugs по дате отправления: