From owner-freebsd-doc@freebsd.org Fri Feb 19 07:44:25 2016 Return-Path: Delivered-To: freebsd-doc@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 2C924AAD316 for ; Fri, 19 Feb 2016 07:44:25 +0000 (UTC) (envelope-from razmyslov@viva64.com) Received: from s24sixth.in-solve.ru (s24sixth.in-solve.ru [81.177.160.5]) by mx1.freebsd.org (Postfix) with ESMTP id 58F2D1A5F for ; Fri, 19 Feb 2016 07:44:23 +0000 (UTC) (envelope-from razmyslov@viva64.com) Received: from Spooler by s24sixth.in-solve.ru (Mercury/32 v4.52) ID MO002CEB; 19 Feb 2016 10:44:24 +0300 Received: from spooler by mail.in-solve.hidden (Mercury/32 v4.52); 19 Feb 2016 10:44:17 +0300 Received: from mail.in-solve.hidden (10.0.1.27) by mail.1gb.ru (Mercury/32 v4.52) with ESMTP ID MG002CE6; 19 Feb 2016 10:44:14 +0300 Received: from Spooler by mail.in-solve.hidden (Mercury/32 v4.52) ID MO001565; 19 Feb 2016 10:44:14 +0300 Received: from spooler by mail.in-solve.hidden (Mercury/32 v4.52); 19 Feb 2016 10:44:07 +0300 Received: from [192.168.1.87] (91.206.72.109) by mail.1gb.ru (Mercury/32 v4.52) with ESMTP ID MG001562; 19 Feb 2016 10:44:00 +0300 Subject: Re: Checking FreeBSD kernel with static analyzer To: Russell Haley , Warren Block References: <20160218165425.4382803.23287.3091@gmail.com> Cc: Fehmi Noyan ISI , Andrey Karpov , freebsd-doc@FreeBSD.org From: Svyatoslav Razmyslov Message-ID: <56C6C7BC.2050302@viva64.com> Date: Fri, 19 Feb 2016 10:43:56 +0300 User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:38.0) Gecko/20100101 Thunderbird/38.6.0 MIME-Version: 1.0 In-Reply-To: <20160218165425.4382803.23287.3091@gmail.com> Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 8bit X-BeenThere: freebsd-doc@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Documentation project List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 19 Feb 2016 07:44:25 -0000 We used the same compiler to build the kernel and to preproccess the files, but adding the '-E' flag to the compilation parameters. 18.02.2016 19:54, Russell Haley пишет: > Okay, are those false positives being documented somehow for future reference? If you don't have a bug report nobody knows next time the analyzer is run. Or worse an hack like me is looking at the code! even a code comment might be a good idea about why it's okay? > > Not releasing the bug list immediately was a wise decision IMHO. > > Svyatoslav, Is your pre-processor harness open or closed source?‎ > > Russ > > Sent from my BlackBerry 10 smartphone on the Koodo network. > Original Message > From: Warren Block > Sent: Thursday, February 18, 2016 6:47 AM > To: Svyatoslav Razmyslov > Cc: Russell Haley; Fehmi Noyan ISI; Andrey Karpov; freebsd-doc@FreeBSD.org > Subject: Re: Checking FreeBSD kernel with static analyzer > > On Thu, 18 Feb 2016, Svyatoslav Razmyslov wrote: > >> I have sent the file in CSV format (PVS-Studio-log-freebsd.csv). Does it work >> for you? >> >> 18.02.2016 11:24, Russell Haley пишет: >>> Svyatoslav, >>> >>> Is there an output format for the issue report that could be massaged in >>> python or lua or the like and submitted or imported through bugzilla? CSV, >>> xml, json? > The mailing list stripped the attachment, although the mail direct to me > included it. The review has been of the text file. We can make the CSV > available. > > Automated creation of bug reports from these results might not be too > useful. Many are only suspected problems and turn out to be false > positives. > -- Svyatoslav Razmyslov "Program Verification Systems" (Co Ltd)