clusterfuzzlite icon indicating copy to clipboard operation
clusterfuzzlite copied to clipboard

Possible to continue fuzzing despite errors?

Open sudden6 opened this issue 3 years ago • 2 comments

Hi,

Is there a setting to continue fuzzing and ignore crashes? Possibly deduplicating the crashes?

Currently the fuzzer stops at the first found crash, but this is not very helpful if there are multiple possible crashes.

sudden6 avatar Feb 20 '22 21:02 sudden6

Unfortunately this setting isn't available right now.

@jonathanmetzman WDYT?

oliverchang avatar Feb 23 '22 04:02 oliverchang

libFuzzer doesn't really do well at continuing fuzzing after a crash. And using deduplication here goes against the "lite" philosophy behind CFLite. So if we were to continue fuzzing it would have to be with other fuzz targets. That is basically being asked for in https://github.com/google/clusterfuzzlite/issues/85 I plan to implement that requested feature by mid March

Thank you, Jonathan

On Tue, Feb 22, 2022 at 11:46 PM Oliver Chang @.***> wrote:

Unfortunately this setting isn't available right now.

@jonathanmetzman https://github.com/jonathanmetzman WDYT?

— Reply to this email directly, view it on GitHub https://github.com/google/clusterfuzzlite/issues/90#issuecomment-1048446096, or unsubscribe https://github.com/notifications/unsubscribe-auth/AHPG6LR7H6LPVCO6RJIUSS3U4RRB5ANCNFSM5O462VVA . Triage notifications on the go with GitHub Mobile for iOS https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 or Android https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.

You are receiving this because you were mentioned.Message ID: @.***>

jonathanmetzman avatar Feb 23 '22 18:02 jonathanmetzman