Date: Tue, 24 Oct 2017 11:46:46 +0200 From: Michael Tuexen <tuexen@freebsd.org> To: David Chisnall <theraven@FreeBSD.org> Cc: Kurt Jaeger <lists@opsec.eu>, FreeBSD Current <freebsd-current@freebsd.org> Subject: Re: libfuzzer support Message-ID: <BBFE1BC3-377D-47AB-87C7-FC49B1C8FC94@freebsd.org> In-Reply-To: <1EFB3A70-094B-4EC3-BE50-66071FE44C65@FreeBSD.org> References: <93FB13F4-CA2D-4AF7-A8F6-F97B38B7D1A0@freebsd.org> <20171024092949.GB34891@home.opsec.eu> <1EFB3A70-094B-4EC3-BE50-66071FE44C65@FreeBSD.org>
next in thread | previous in thread | raw e-mail | index | archive | help
> On 24. Oct 2017, at 11:31, David Chisnall <theraven@FreeBSD.org> = wrote: >=20 > On 24 Oct 2017, at 10:29, Kurt Jaeger <lists@opsec.eu> wrote: >>=20 >>>=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. >>=20 >> But that would probably(?) be the best place to add it first. >=20 > It=E2=80=99s been a while, but I=E2=80=99m pretty sure I had libFuzzer = working from the upstream sources on FreeBSD. I found AFL (which also = works on FreeBSD out of the box) more useful, so I didn=E2=80=99t=20 Are there plans to enable it for the versions of clang integrated in = FreeBSD? > spend much time with it. Thanks for the hint, will look into it. Best regards Michael >=20 > David >=20
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?BBFE1BC3-377D-47AB-87C7-FC49B1C8FC94>