Skip site navigation (1)Skip section navigation (2)
Date:      Thu, 18 Feb 2016 23:02:19 -0800
From:      Russell Haley <russ.haley@gmail.com>
To:        Warren Block <wblock@wonkity.com>, Svyatoslav Razmyslov <razmyslov@viva64.com>
Cc:        Fehmi Noyan ISI <fnoyanisi@yahoo.com>, Andrey Karpov <karpov@viva64.com>, freebsd-doc@freebsd.org
Subject:   Re: Checking FreeBSD kernel with static analyzer
Message-ID:  <CABx9NuT8N4uavL0CxRkm5_7gCywgW8raQr2BMnThOMW0JknuRw@mail.gmail.com>
In-Reply-To: <20160218165425.4382803.23287.3091@gmail.com>
References:  <20160218165425.4382803.23287.3091@gmail.com>

next in thread | previous in thread | raw e-mail | index | archive | help
Thanks warren, send me the csv when you get a chance. I'd really
appreciate it. You implied in previous emails that there is a larger
discussion going on about reviewing the data. Is there a public chat
anywhere? I see this as an excellent learning tool for studying the
code.

Thanks,

Russ

On Thu, Feb 18, 2016 at 8:54 AM, Russell Haley <russ.haley@gmail.com> wrote=
:
> Okay, are those false positives being documented somehow for future refer=
ence? 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?=E2=80=8E
>
> 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.or=
g
> 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 =D0=BF=D0=B8=D1=88=D0=B5=D1=82:
>>> Svyatoslav,
>>>
>>> Is there an output format for the issue report that could be massaged i=
n
>>> python or lua or the like and submitted or imported through bugzilla? C=
SV,
>>> 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.



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CABx9NuT8N4uavL0CxRkm5_7gCywgW8raQr2BMnThOMW0JknuRw>