From owner-freebsd-current@freebsd.org Tue Oct 24 09:41:47 2017 Return-Path: Delivered-To: freebsd-current@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 3B576E46D21 for ; Tue, 24 Oct 2017 09:41:47 +0000 (UTC) (envelope-from tuexen@freebsd.org) Received: from drew.franken.de (mail-n.franken.de [193.175.24.27]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "*.franken.de", Issuer "COMODO RSA Domain Validation Secure Server CA" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 01CA37C232 for ; Tue, 24 Oct 2017 09:41:46 +0000 (UTC) (envelope-from tuexen@freebsd.org) Received: from nod162.eduroam.kau.se (nod162.eduroam.kau.se [130.243.28.162]) (Authenticated sender: macmic) by mail-n.franken.de (Postfix) with ESMTPSA id A337D72106C16; Tue, 24 Oct 2017 11:41:36 +0200 (CEST) Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (Mac OS X Mail 11.0 \(3445.1.7\)) Subject: Re: libfuzzer support From: Michael Tuexen In-Reply-To: <20171024092949.GB34891@home.opsec.eu> Date: Tue, 24 Oct 2017 11:41:34 +0200 Cc: FreeBSD Current Content-Transfer-Encoding: quoted-printable Message-Id: <6C1027C2-F1E2-4B8A-9ABC-3E95E76CDE1F@freebsd.org> References: <93FB13F4-CA2D-4AF7-A8F6-F97B38B7D1A0@freebsd.org> <20171024092949.GB34891@home.opsec.eu> To: Kurt Jaeger X-Mailer: Apple Mail (2.3445.1.7) X-Spam-Status: No, score=-2.9 required=5.0 tests=ALL_TRUSTED,BAYES_00 autolearn=disabled version=3.4.1 X-Spam-Checker-Version: SpamAssassin 3.4.1 (2015-04-28) on mail-n.franken.de X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 24 Oct 2017 09:41:47 -0000 > On 24. Oct 2017, at 11:29, Kurt Jaeger wrote: >=20 > Hi! >=20 >> is libfuzzer (see https://llvm.org/docs/LibFuzzer.html) supported on = FreeBSD head? >> It seems that it is not supported by /usr/bin/clang... >>=20 >> Am I wrong and it is supported or is someone working on it? >=20 > I searched in the Port devel/llvm50 and it looks like there's no = support > for libfuzzer right now. Yepp, I checked that also... >=20 > But that would probably(?) be the best place to add it first. Not sure. It would be nice if some version of clang would support this, I do not care if it is the one in the base system or in the ports tree. Best regards Michael >=20 > --=20 > pi@opsec.eu +49 171 3101372 3 years = to go !