Skip site navigation (1)Skip section navigation (2)
Date:      Mon, 5 Oct 2015 17:48:49 -0600
From:      Alan Somers <asomers@freebsd.org>
To:        Jan Knepper <jan@digitaldaemon.com>
Cc:        Alan Somers <asomers@freebsd.org>, Thomas Schmitt <scdbackup@gmx.net>,  "freebsd-hackers@freebsd.org" <freebsd-hackers@freebsd.org>
Subject:   Re: Which program produces FreeBSD-11.0-CURRENT-amd64-*-disc1.iso ?
Message-ID:  <CAOtMX2j3Qk9PDvKW5oQHTnLjsPFgmb2f-uQZGkPpOPC=bQYbbg@mail.gmail.com>
In-Reply-To: <62905755-63CE-430E-A6AA-D3FCE3EF347A@digitaldaemon.com>
References:  <CAOtMX2jmt4oOjhEZezY9a4EokkO5eHJ2gVnsRUEt5UPG_NUQ5Q@mail.gmail.com> <16694582476300143275@scdbackup.webframe.org> <CAOtMX2in1NZuD-qE8NrZ3-tGf2sLSzf77R_v7ZrFCc0=k%2BDkpA@mail.gmail.com> <62905755-63CE-430E-A6AA-D3FCE3EF347A@digitaldaemon.com>

next in thread | previous in thread | raw e-mail | index | archive | help
Well, yes you are correct.  I should've said, "of the languages in use
by FreeBSD, Coverity can only check C and C++".  The Ports tree is
mostly makefiles.

-Alan

On Mon, Oct 5, 2015 at 4:57 PM, Jan Knepper <jan@digitaldaemon.com> wrote:
> 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@freebsd.org> wrote:
>>
>>> On Mon, Oct 5, 2015 at 1:02 PM, Thomas Schmitt <scdbackup@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@freebsd.org mailing list
>> https://lists.freebsd.org/mailman/listinfo/freebsd-hackers
>> To unsubscribe, send any mail to "freebsd-hackers-unsubscribe@freebsd.org"



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