README clarification around language support about clusterfuzz HOT 7 CLOSED

You are right that fuzzing/ClusterFuzz is language agnostic.

But I think we did this intentionally (CC @oliverchang).

We've only used ClusterFuzz for fuzzing C/C++ (and a small amount of rust), so we're only confident that with our docs it's easy to setup fuzzing for these kinds of programs.

While we would love it if people started using ClusterFuzz for fuzzing safe programming languages (some possible use cases here), we don't want to give people the impression that this is something they can easily use to improve their JS/Python etc. code.

from clusterfuzz.

If you can find good memory instrumentation for those languages, it is pretty easy to extend ClusterFuzz to detect those crashes (just some parsing signatures in stack_analyzer.py). Infrastructure wise, you can run any program on Linux, Windows and Mac.

from clusterfuzz.

Hey everyone, is this an issue I could work on possibly ? would be a good start as my first contribution here.
/cc: @inferno-chromium @jonathanmetzman @rudolfolah

from clusterfuzz.

I don't think so since IMO we did this intentionally.
Closing this issue, but if @inferno-chromium disagrees he can reopen.

from clusterfuzz.

Actually, it may be worth mentioning language agnostic part to appeal to go users or users of other languages that already have fuzzer support. Frankly, I don't even know if the tooling for Ruby/Python exists for them to even be integrated into ClusterFuzz. I think for clarity's sake we should say ClusterFuzz supports C/C++ and Rust and supporting go or LLVM-based languages should be doable.
@co16353sidak I don't think this is a good first issue unfortunately.

from clusterfuzz.

Okay @jonathanmetzman , although would love it if there were any first issue based work here as I would love to start doing some work while understanding the code of this PR

from clusterfuzz.

@jonathanmetzman thanks for updating the FAQ, think this resolves this issue! 😄

from clusterfuzz.