Checking FreeBSD kernel with static analyzer

[Russell Haley]

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 at gmail.com> wrote:
> 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 at 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.