Re: git and the Clang Static Analyzer

On Mon, May 08, 2017 at 09:26:11PM +0200, Дилян Палаузов wrote: > Click on https://mail.aegee.org/dpa/scan-build-git-4fa66c85f11/ and > then on "fast-import.c: line 2057 -> View Report" and you will see > pointless assignment. > > I cannot organize the report much better, as filtering out the

Re: git and the Clang Static Analyzer

Hello Johannes, I compiled git/master ... which advances from time to time, so you definitely want to include a more informative data point here, e.g. 4fa66c85f11 (Git 2.13-rc2, 2017-05-04) ... The 4fa66c85f11 you mentioned is part of the URL I sent. Please note, that the information is

Re: git and the Clang Static Analyzer

> On 08 May 2017, at 12:12, Johannes Schindelin > wrote: > > Hi Dilyan, > > > On Sun, 7 May 2017, Дилян Палаузов wrote: > >> ... > > Also: to make it *really* useful for other developers, it would be a good > idea for you to try your hand at patching the

Re: git and the Clang Static Analyzer

Hi Dilyan, On Sun, 7 May 2017, Дилян Палаузов wrote: > I compiled git/master ... which advances from time to time, so you definitely want to include a more informative data point here, e.g. 4fa66c85f11 (Git 2.13-rc2, 2017-05-04) ... > using the clang 4.0 static analyzer with > > scan-build

git and the Clang Static Analyzer

Hello, I compiled git/master using the clang 4.0 static analyzer with scan-build ./configure --with-libpcre --with-openssl scan-build make and here are the results: https://mail.aegee.org/dpa/scan-build-git-4fa66c85f11/ Please note, that the information is only about what gets actually