- Similar to that of clang-fuzzer itself but instead only targets Objective-C source files via cc1
- Also adds an example corpus directory containing some input for Objective-C
It's similar at the moment (was initially going to add more flags), but I could swap it over to read an integer/Boolean to swap between the two languages. If we want to modify them in the future (which we might be interested in depending on how well this works) it probably makes sense to keep them separate though.
|19 ↗||(On Diff #225633)|
Nit: Since it does nothing, let's omit the LLVMFuzzerInitialize definition.
|22 ↗||(On Diff #225633)|
|50 ↗||(On Diff #225633)|
Since this is ~identical to handle_cxx, I'd like to reuse the implementation. Can we make a more generic function (e.g., handleLanguage(Language type, ...)) and use it for both?
Looks reasonable to me. The duplication is unfortunate, but it is reasonable while we have two binaries.
However, you could explore reading the command line flags for HandleCXX in LLVMFuzzerInitialize from fuzzer's command line flags.
It is superfluous on Linux at least since libFuzzer defines its own weak definition. I'm not sure how it works for Windows.
I'm fine if you want to add it back in here.