AFLplusplus / AFLplusplus/LibAFL

Objective Deduplication using the stack/call trace helper for QemuForkExecutor

未关闭
#1,644 1 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看
主要语言
Rust
星标
2.6k
派生
481
平均合并
2 天 30 分钟
30 天内合并 PR
16

描述

I'm trying to implement a deduplication objective using existing crash hash, stack/call trace helper, and related objectives. The challenge is, I'm doing this for the QemuForkExecutor, and as expected, the default call trace helper in Qemu seems to have been designed for the in-process executor, and using it with a QemuForkExecutor will crash the fuzzer. I still trying to understand the inner working of LibAFL, so I was thinking about simply copying the existing helper and setting const HOOKS_DO_SIDE_EFFECTS: bool = false;. Would this be a problem? I am trying to avoid using the HitCounts map for deduplication because we could have the same crash, with the same call/stack trace but different edge hit counts, and I suppose a deduplication feedback based on the Hitcounts map woud consider such a scenario as unique crashes.
Any ideas on how to go about this would be very much appreciated.
Thanks a lot in advance.

贡献指南

打开贡献指南

评估

这个 Issue 还没有评估数据。

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。