[llvm-dev] Fuzzing bitcode reader

[Mehdi Amini via llvm-dev]

> On Feb 1, 2017, at 8:58 AM, Michael Kruse <llvmdev at meinersbur.de> wrote:
> 
> 2017-02-01 17:45 GMT+01:00 Mehdi Amini <mehdi.amini at apple.com>:
>> 
>>> On Feb 1, 2017, at 8:34 AM, Michael Kruse via llvm-dev <llvm-dev at lists.llvm.org> wrote:
>>> 
>>> 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).
>> 
>> Isn’t it this stage? http://lab.llvm.org:8011/builders/sanitizer-x86_64-linux-fuzzer/builds/2755/steps/stage2%2Fasan%2Bassertions%20check-fuzzer/logs/stdio
> 
> To me it looks like just the compilation and the unit+regression tests
> ("ninja check-fuzzer", not even depending on clang). It also completes
> in only 10 minutes, which is not a lot for fuzzing.

Yes, I believe you’re right!

— 
Mehdi