monitor is empty

[AxiaoJJ]

Hi, there

The run.sh script was used to launch afl++ and mopt, testing all targets. However, in some cases, the log files show numerous bugs, but there is only one 5 file in the monitor folder. The files in the findings directory indicate that the fuzzer is running successfully with some crashes.

[adrianherrera]

Hi there,

Are the crashes just duplicates? Or are you saying that new bugs are not being recorded correctly? Further details would help diagnose the issue.

[AxiaoJJ]

I ran the OpenSSL server with aflplusplus for 24 hours, but the monitor only contains a single '5'. It seems like nothing got recorded.

[adrianherrera]

Oh I think I understand.

The magma "crashes" do not generate a typical AFL crash (because this is not generic across fuzzers, and does not measure a fuzzer's detection capabilities). You shouldn't look at the afl log for crash data, because this will not be reflective of the magma bugs. Instead, you should use the provided scripts to analyze and understand crashes.

Hope this helps!

[AxiaoJJ]

But the monitor has only empty file, which cannot be analyzed.

[adrianherrera]

How long are you running the fuzzer for? Are you comparing your results against previous published results? What is the output of the report scripts? It could just be that you found none of the injected bugs in that target.

[xubenji]

Oh I think I understand.

The magma "crashes" do not generate a typical AFL crash (because this is not generic across fuzzers, and does not measure a fuzzer's detection capabilities). You shouldn't look at the afl log for crash data, because this will not be reflective of the magma bugs. Instead, you should use the provided scripts to analyze and understand crashes.

Hope this helps!

With that being said, how can we analysis lava bugs?