Simonas Kazlauskas

old versions of rustc nightly are not supported with new versions of cargo-fuzz. Please upgrade rustc.

(that’s because the actual json crate is in another subdirectory within the checkout)

Please provide a more minimal reproducer. Preferably something that does not involve pulling down the entirety of the google’s oss fuzz project, invokes cargo directly, etc. The more external variables...

> published on crates.io libfuzzer-sys was consciously not published, but I guess it doesn’t matter either way, as long as the ownership of the crate belongs to the same owners...

(it doesn't build right now because there are some changes wrt visibility within macro, which I didn't consider a good expenditure of time, given the other observations)

Returning to this, I think it might be worthwhile to do this. Among other things that this can enable is e.g. an ability to specify certain fuzzing-related parameters within the...

The libFuzzer changes should be implemented upstream first. It is desirable to not diverge from upstream libFuzzer at all.

We could `-Dmain=libfuzzer_main` or something along those lines. It can then also be made optional through build-time features. I'll see about making a PR for this today.

Using internals is fine, given that we bundle libfuzzer within this project anyway. Though, what should be done is adding a separate .cpp file to the vendored libfuzzer copy that...

This appears to be related to `-Cpanic=abort` panic strategy.