AFLplusplus / AFLplusplus/libafl_fuzzbench

Grimoire stops running after a few snapshots in FuzzBench

未關閉
#14 6 則留言 0 個 reaction 已指派 0 人 在 GitHub 檢視
主要語言
Rust
星號
12
分支
8
PR 合併指標
30 天內沒有已合併 PR

描述

I'm trying to run a FuzzBench experiment on the mruby target after applying https://github.com/google/fuzzbench/pull/2048 and https://github.com/AFLplusplus/libafl_fuzzbench/pull/13. After applying these patches, the experiment starts successfully, and I get reasonable results from the first few snapshots (the corpus directories contain Ruby-like test cases, and the coverage increases).

However, after several snapshots, it seems that nothing happens anymore. I receive some heartbeat messages in the log, but the corpus directories remain empty, and the coverage stops increasing. This issue occurred in all 5 out of 5 trials after 30 to 60 minutes of fuzzing.

My guess is that there's an issue with the crash, timeout, or restart handling of the SUT (even though it appears to be similar to other grammar-aware fuzzer implementations like Nautilus, Gramatron, and token-level fuzzers, which work fine). Alternatively, it could be a problem with the mutator implementation. Unfortunately, I'm not familiar with Rust or the Grimoire implementation.

Has anyone faced a similar issue or have any idea what might be happening here?

貢獻指南

這個儲存庫沒有索引到貢獻指南

評估

這個 Issue 還沒有評估資料。

把新 issue 寄到你的電子郵件信箱

精選適合新手參與的 GitHub issue 摘要。