[PATCH] D70738: [libFuzzer] Add custom output function

[Manish Goregaokar via Phabricator via llvm-commits]

Manishearth added a comment.

In D70738#1773465 <https://reviews.llvm.org/D70738#1773465>, @Dor1s wrote:

> In Chromium we recommend fuzz target authors do something like this (https://cs.chromium.org/chromium/src/testing/libfuzzer/fuzzers/javascript_parser_proto_fuzzer.cc?l=63&rcl=f88381726e8673b289d79dde6af1b6b7f1ab063a):


The problem with approaches like this is that you still need to identify the last failing use case and run it a second time. With this patch the user experience is very smooth: the failing string is formatted and printed immediately.

It feels to me that we're using libFuzzer a bit differently from y'all, with different goals on usability. The workarounds mentioned so far are very suboptimal :/

We're hoping to make fuzzing as easy as possible for random maintainers to quickly set up, as opposed to us maintaining a lot of fuzz targets written in a uniform way.


Repository:
  rCRT Compiler Runtime

CHANGES SINCE LAST ACTION
  https://reviews.llvm.org/D70738/new/

https://reviews.llvm.org/D70738