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

[Manish Goregaokar via Phabricator via llvm-commits]

Manishearth added a comment.

> Oh, why do you need to print it every time fuzz target hits a crash? It should be an option controlled during runtime, so that users or an automated infrastructure can easily turn it on when reproducing an individual crash.

I don't understand why you _wouldn't_ want to: why do we print three different representations of the binary fuzz data each time the target hits the crash? This would be for the same reason.

The vast majority of workflows for Rust fuzzing is to run `cargo fuzz name_of_target` and look at the output of libFuzzer.


Repository:
  rCRT Compiler Runtime

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

https://reviews.llvm.org/D70738