From owner-freebsd-hackers@freebsd.org Mon Oct 5 21:04:48 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 DF36599A5AE for ; Mon, 5 Oct 2015 21:04:48 +0000 (UTC) (envelope-from asomers@gmail.com) Received: from mail-oi0-x22f.google.com (mail-oi0-x22f.google.com [IPv6:2607:f8b0:4003:c06::22f]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id B7841640 for ; Mon, 5 Oct 2015 21:04:48 +0000 (UTC) (envelope-from asomers@gmail.com) Received: by oiww128 with SMTP id w128so98154022oiw.2 for ; Mon, 05 Oct 2015 14:04:48 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date:message-id:subject :from:to:cc:content-type; bh=oxIlAlxyX6co9FtqrN4xO3WrNC+YEx0GjPyCN6kA9Lg=; b=Z39wvCPLJZJO+2783YBN4ALbTaSIqD/iw+JwEfSKpL+HzNImkZ5o5SFGpdoBIPz6LY Glc7IZdlcximJfqdYrweCbvjEyaCIpE8QTUijs9vSXaD4ktlXKj0kX2K0zVm5Tu4UvQR ugY2iqrNNLleVzVY/A4mYplzdsV5d3RthsIHVThI8TXCLi+6n0ZaJTPdceT7kBFuBM6e 4Z43PRu/ZftvHmd8TWxwxGR3UIQCRCOwB86a2yIql9wRfF+HANdV1jWQuGE3rBCW4jRv 1xUXrniniT7GoVQrp0k400O/XC09r9Z/zhonrs8K9Rgb5xaA5H/46e0pcVVBsiiBccy/ Lk4A== MIME-Version: 1.0 X-Received: by 10.202.228.210 with SMTP id b201mr17820404oih.100.1444079087808; Mon, 05 Oct 2015 14:04:47 -0700 (PDT) Sender: asomers@gmail.com Received: by 10.202.71.6 with HTTP; Mon, 5 Oct 2015 14:04:47 -0700 (PDT) In-Reply-To: <16694582476300143275@scdbackup.webframe.org> References: <16694582476300143275@scdbackup.webframe.org> Date: Mon, 5 Oct 2015 15:04:47 -0600 X-Google-Sender-Auth: dUb2DaM-YeXObhJbx680nb9lvZM Message-ID: Subject: Re: Which program produces FreeBSD-11.0-CURRENT-amd64-*-disc1.iso ? From: Alan Somers To: Thomas Schmitt Cc: "freebsd-hackers@freebsd.org" Content-Type: text/plain; charset=UTF-8 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 21:04:49 -0000 On Mon, Oct 5, 2015 at 1:02 PM, Thomas Schmitt 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