Skip to content

Track reached targets in printed AFLGo statics - #3

Open
wrsturgeon wants to merge 1 commit into
vusec:masterfrom
wrsturgeon:master
Open

Track reached targets in printed AFLGo statics#3
wrsturgeon wants to merge 1 commit into
vusec:masterfrom
wrsturgeon:master

Conversation

@wrsturgeon

Copy link
Copy Markdown

Hi,

Thanks for this great library.

I started using LibAFLGo today to experiment with instrumenting Rust binaries, and I noticed that reached targets are often not printed after they have in fact been reached, e.g. in the following format:

[Testcase #0] run time: 0h-0m-0s, clients: 1, corpus: 10, objectives: 0, executions: 4843, exec/sec: 0.000, distance_min: 5, edges: 10/11 (90%), distance_max: 9, targets: 0/256 (0%)

Assuming I understand the situation correctly, I was able to fix this by changing one line, /fuzzers/aflgo/src/lib.rs:264:

-    let targets_feedback = MaxMapFeedback::new(&targets_observer);
+    let targets_feedback = MaxMapFeedback::tracking(&targets_observer, false, true);

Full disclosure: this was found and patched by GPT-5.6 Terra, but I have independently tested the patch on a toy program, and it works.

Please let me know if this was helpful, or if I'm misunderstanding something!

Best,
Will

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant