From owner-freebsd-hackers@freebsd.org Mon Oct 5 19:00:50 2015 Return-Path: Delivered-To: freebsd-hackers@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 6D0CC99A395 for ; Mon, 5 Oct 2015 19:00:50 +0000 (UTC) (envelope-from scdbackup@gmx.net) Received: from mout.gmx.net (mout.gmx.net [212.227.17.20]) (using TLSv1.2 with cipher DHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mout.gmx.net", Issuer "TeleSec ServerPass DE-1" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 2B9CF7D4 for ; Mon, 5 Oct 2015 19:00:49 +0000 (UTC) (envelope-from scdbackup@gmx.net) Received: from scdbackup.webframe.org ([79.192.94.39]) by mail.gmx.com (mrgmx101) with ESMTPSA (Nemesis) id 0MMXVC-1ZhXdP3GOc-008G0N for ; Mon, 05 Oct 2015 21:00:41 +0200 Date: Mon, 05 Oct 2015 21:02:08 +0200 From: "Thomas Schmitt" To: freebsd-hackers@freebsd.org Subject: Re: Which program produces FreeBSD-11.0-CURRENT-amd64-*-disc1.iso ? Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 8bit References: In-Reply-To: Message-Id: <16694582476300143275@scdbackup.webframe.org> X-Provags-ID: V03:K0:6ZHSJpo2mjA29fevE9BAsiaeq3N/Wdk7sSTK6j75/mHpnpzkv/N UR/Z7+hycslyWsG7bcKgf3QRMlF9+wC7ECkLIfyDp8xDKwUpExa3OyIko14cikwv5vni9Nm kabyn8MbTops1FUnOH5e+Q5iRT1GYxEqxrGSyWKzrCNUM3MWYsFPCxTmADv+9RQ0AnlGI+V PGrzJ9uVYtzzYv4m92hrA== X-UI-Out-Filterresults: notjunk:1;V01:K0:G1YpWrxxWeg=:mR5zB3j8Tt0fpxeL+QNTfP oqbtVt846sWe+C3f5Z8UBmJ0Ehj+7DF5k//bMj7MuW8xs6q1mRJg9C995xf4iweVp/e8UD60l NXod0qT0vFglQTZVAGysoaVKx9geMtjdq1ZVxC/IVBZ/VRfvfKePNEjgON+UAxR0e0eCBoowG NhR4Dw68YpSKFexQC6f278IqK97UXkftBpYYWdApfB2ePCnsHgDAgAbkmXAzfxQI8pKF0zj1R hUqKeSMxJXN4+2iuIrsiUavHBkpkxWfBZYBUAkRh68Ll/S2JXjjHnh7BOAyYDd7koIxYqnvz3 qoOGeB4jd2lLtqZ7O5qpRSSxTa/s2vwaQsXvzzwVCidrgFl0IvZQcXNKIwFdgnid4l+9rcy6n fn/+EpfFfGIPFK7suNNMvpLJrPkPvGIrzOR4gePaBt7gYqGAPKsTFScFIlGmCVRv+u4okTyrP sWMz0XzvpVCpninMPoPGQwIyHzrVpfMP7w1DN5CXyLRS7B98J8AMpIuq0WeTI1EzyFSLx8PIm J2UaGCQjwVBdGLwFHSwN/Qz4QM1/obp6KjtYm8KbaTGYh/gPc7X3dCWhPMXaj8XzWhdTImUj7 GAPm0tL0bNl/d4A8Cjl1Gtwh2gJ4QJ4jUqsnc2AUwr3K9enATc48mk9IdjkTSnArJ9mXTlNhP 1L0K5oZnICFpNZRRqLR22lfxuZxLxqM886CjVkDB8V8dgfhx3riexrSfQzoxHPMagTTtEnGiL 4rQWPC9MKum4yyameQ82VaAU/yQpNjuZAiC0+4P42GbUoNNV2hW5ledwjEu6uQqpm3cBH94tj lJIpXtQ X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 05 Oct 2015 19:00:50 -0000 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