Closed addisoncrump closed 9 months ago
having some linkage issues
Found an issue with one of our recent optimisations. Marked as draft until it's fixed up.
Good to go! Hunted down all the bugs with the recent optimisations (that I'm aware of... :skull:)
libafl_libfuzzer is not affected by the issue identified in #1902 because we don't use libafl_cc, so this is good to go whenever y'all are ready to fire the experiment.
Rebased on the libafl updates used in #1902 for sanity.
Hi @addisoncrump, is this ready for experiments?
If so, would you mind making a trivial modification to service/gcbrun_experiment.py? This will allow me to launch experiments in this PR. Here is an example to add a dummy comment : ) Thanks!
In addition, could you please write your experiment request in this format?
You can swap the --experiment-name
and --fuzzers
parameters with your values.
I would really appreciate that : )
For example, I reckon the command for this case is:
/gcbrun run_experiment.py -a --experiment-config /opt/fuzzbench/service/experiment-config.yaml --experiment-name 2023-10-05-libafl_best --fuzzers libafl_libfuzzer_best libafl_libfuzzer
Where FuzzBench will reuse existing results of aflplusplus
and libfuzzer
.
We have a couple of more changes in the queue ready, so I'll send this in in a bit :slightly_smiling_face:
this is ready with all the pr merged? @addisoncrump
Yup, let me update the commit
All of the relevant libafl changes landed, so I removed libfuzzer_best. For now, this is good to go :heavy_check_mark:
Let's compare:
Thanks!
Well, that didn't work. Coming back to this in the morning.
Superceded by other recent PRs.
We made some heavy optimisations and new features that we'd like to test. Can an experiment be run for:
libafl (depends on #1902; temporarily rebased)please skip while we remediatelibafl_cc
Thanks!