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

[Max Moroz via Phabricator via llvm-commits]

Dor1s added a comment.

If you're running fuzz targets manually, then it makes sense -- you need to type one command less to print the crash input. Although it seems like `cargo fuzz` can do that for you as well, so it will be still a single command.

Once you start automating things and run fuzz targets at scale, you won't need to look into the input until the following is done:

1. verify reproducibility
2. perform deduplication
3. minimize the input

Also note that the same crashes will be hit many times if you run fuzz targets in parallel. That's why it's better not to print the input every time a fuzz target crashes.


Repository:
  rCRT Compiler Runtime

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

https://reviews.llvm.org/D70738