Date: Mon, 05 Oct 2015 21:02:08 +0200 From: "Thomas Schmitt" <scdbackup@gmx.net> To: freebsd-hackers@freebsd.org Subject: Re: Which program produces FreeBSD-11.0-CURRENT-amd64-*-disc1.iso ? Message-ID: <16694582476300143275@scdbackup.webframe.org> In-Reply-To: <CAOtMX2jmt4oOjhEZezY9a4EokkO5eHJ2gVnsRUEt5UPG_NUQ5Q@mail.gmail.com> References: <CAOtMX2jmt4oOjhEZezY9a4EokkO5eHJ2gVnsRUEt5UPG_NUQ5Q@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?16694582476300143275>