Which program produces FreeBSD-11.0-CURRENT-amd64-*-disc1.iso ?

[Jan Knepper]

Actually... Coverity also can check Java, C#, JavaScript and Objective-C.

The group I work for at the FAA uses it for C/C++

Jan



ManiaC++
Jan Knepper

> On Oct 5, 2015, at 17:04, Alan Somers <asomers at freebsd.org> wrote:
> 
>> On Mon, Oct 5, 2015 at 1:02 PM, Thomas Schmitt <scdbackup at gmx.net> wrote:
>> Hi,
>> 
>>> the FreeBSD project has had a free Coverity account for a
>>> few years now.
>> 
>> Does it also get applied to ports ?
>> Especially i would be interested in my own upstream stuff:
>>  http://portsmon.freebsd.org/portoverview.py?category=devel&portname=libburn
>>  http://portsmon.freebsd.org/portoverview.py?category=devel&portname=libisofs
>>  http://portsmon.freebsd.org/portoverview.py?category=sysutils&portname=xorriso
>> 
>> Meanwhile i filed
>>  https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=203531
>> 
>> Problem #1 would be a candidate for Coverity.
>>  "Uninitialized malloc memory in timestamp of root directory."
>> 
>> The other three problems are decisions at the discretion of
>> the programmer. We will have to wait a few more years before
>> automats can tell us that we got the specs wrong or try to
>> save a few bytes where it is not worth the hassle.
>> 
>> 
>>> Would it be possible to get Thomas an account?
>> 
>> A list of my own errors would not really be welcome but in
>> any case appreciated. :))
>> 
>> A Coverity run over makefs would make sense if my proposals
>> get implemented in some way. I hope they are safe, but one
>> never knows.
>> 
>> 
>> Have a nice day :)
>> 
>> Thomas
> 
> Nope. Coverity only runs on CURRENT.  It only knows how to check C and
> C++ code, so it wouldn't be very useful in ports, anyway.  Thanks a
> lot for the bug report!
> 
> -Alan
> _______________________________________________
> freebsd-hackers at freebsd.org mailing list
> https://lists.freebsd.org/mailman/listinfo/freebsd-hackers
> To unsubscribe, send any mail to "freebsd-hackers-unsubscribe at freebsd.org"