Date: Mon, 5 Oct 2015 21:02:25 -0400 From: Jan Knepper <jan@digitaldaemon.com> To: Alan Somers <asomers@freebsd.org> Cc: 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: <73D2694F-BB8D-4369-8846-3A1056ABD9F9@digitaldaemon.com> In-Reply-To: <CAOtMX2j3Qk9PDvKW5oQHTnLjsPFgmb2f-uQZGkPpOPC=bQYbbg@mail.gmail.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> <CAOtMX2j3Qk9PDvKW5oQHTnLjsPFgmb2f-uQZGkPpOPC=bQYbbg@mail.gmail.com>
index | next in thread | previous in thread | raw e-mail
Well, that would be the bare ports tree. I am presuming that the question was about the ports code that is downloaded and build. There is a lot of C and C++ code among that. It would be great to run Coverity on that as well. However, I personally think that is more the responsibility of the specific port development team... Jan ManiaC++ Jan Knepper > On Oct 5, 2015, at 19:48, Alan Somers <asomers@freebsd.org> wrote: > > 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"help
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?73D2694F-BB8D-4369-8846-3A1056ABD9F9>