clusterfuzz
clusterfuzz copied to clipboard
google
Scalable fuzzing infrastructure.
No one has actually run into this issue.
Some good candidates: 1. Symbolize 2. Regression Once setup.py is completed, let's do: 1. minimize 2. progression
Having clusterfuzz-experimental and having it log errors to a different place is a recipe for hiding bugs. We should make it log to google.com:clusterfuzz or eliminate it entirely (we have...
The main blocker to this is our dependency on python libraries with C extensions ([e.g. protobuf, grpc)](https://github.com/google/clusterfuzz/blob/master/src/platform_requirements.txt)), and the need to bundle them in our deployment zips across Linux, Windows,...
They are causing some scaling issues that need to be addressed. Disable them temporarily and then replace with something that works.
1) If we fuzz with some `-max_len` value, the `initial_edge_coverage` stat will not represent the actual edge coverage of the full corpus, because libFuzzer will ignore the contents past the...
When launching virtual cuttlefish machines, we use the following [code](https://github.com/marktefftech/clusterfuzz/blob/3fdc86d4e13db47b2583468c6d2a28107817bf01/src/clusterfuzz/_internal/platforms/android/adb.py#L422-L424), which specifically disables sandboxing behavior for the Cuttlefish device: ``` launch_cvd_command_line = ( f'sudo {launch_cvd_path} --daemon --memory_mb={device_memory_mb} ' '--report_anonymous_usage_stats=Y --enable_sandbox=true...
https://pantheon.corp.google.com/errors/detail/CMDozKHgzoCLzQE;service=;version=;time=PT6H?e=-13802955&mods=logs_tg_prod&project=google.com:cluster-fuzz https://pantheon.corp.google.com/errors/detail/CKOVw8L-wf7nKQ;service=;version=;time=P7D?project=google.com:cluster-fuzz&e=-13802955&mods=logs_tg_prod
It's pretty useless for developers and we don't even calculate it correctly