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

[Manish Goregaokar via Phabricator via llvm-commits]

Manishearth added a comment.

In D70738#1773189 <https://reviews.llvm.org/D70738#1773189>, @vitalybuka wrote:

> You can consider just to link needed code into small binary which will printout serialized inputs from the drive. And call that e.g. in the following way:


At least in the case of cargo-fuzz this means compiling the fuzz target under two modes, because the way libfuzzer works it has to take over as main. This is really hard to make work under cargo, which is driving all the stuff here. It's fine when you need to compile one binary per fuzz target, but compiling two from the same code requires a lot of invasive changes that are not possible for a cargo wrapper.

> This option existed before, but I don't see that it used a lot.
>  So having that workaround is quite simple I'd prefer to not extend API.

We, at least, can't use this workaround.


Repository:
  rCRT Compiler Runtime

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

https://reviews.llvm.org/D70738