Displaying 2 results from an estimated 2 matches for "33ce1dd8".
2017 Feb 01
3
Fuzzing bitcode reader
Hi all,
The blog entry [1] suggest that one of the buildbots constantly fuzzes
clang and clang-format. However, the actual bot [2] only tests the
fuzzer itself over a well-known set of bugs in standard software (eg.
Heartbleed [3] seems to be among them). Has there actually ever been a
buildbot that fuzzes clang/LLVM itself?
Another (obvious?) fuzzing candidate would be the LLVM's bitcode
2017 Feb 01
2
Fuzzing bitcode reader
...libFuzzer (which is an in-process fuzzer) the
target should not assert/abort/exit on any input (if it's not a bug).
--kcc
>
> —
> Mehdi
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20170201/33ce1dd8/attachment-0001.html>