prosyslab / DAFL-artifact

35 stars 3 forks source link

Help wanted when running the DAFL tool directly in the docker #7

Closed null1024-ws closed 7 months ago

null1024-ws commented 7 months ago

Hi So impressive the performance DAFL has in the directed fuzzing! Recently I tried to run the DAFL in the provided docker using "run-DAFL.sh" script, there is something wrong with the fuzzing instance. The command I used is sudo ./run_DAFL.sh lrzip-ed51e14-2018-11496 "-A -a -l -S -s --special-syms --synthetic --with-symbol-versions -D @@" "file" 60 , the figure containing the error messages is as below. image The fuzzing testing process was aborted by something. The ./common-postproc.sh is in the same directory. So could you kindly help with this?

goodtaeeun commented 7 months ago

Hi, thank you for your interest in DAFL and its artifact!

Try running the script with the absolute path as the following. /tool-script/run_DAFL.sh lrzip-ed51e14-2018-11496 "-A -a -l -S -s --special-syms --synthetic --with-symbol-versions -D @@" "file" 60

null1024-ws commented 7 months ago

Thanks for your advice. I tried this command in the docker environment. There was no problem like "No such file or directory". But the fuzzing instance seemed something abnormal. The total paths always 1; image

goodtaeeun commented 7 months ago

The current command line options you are using are for nm, not lrzip. You can find the appropriate command line options in scripts/benchmark.py. For instance, you should use -t @@ for lrzip https://github.com/prosyslab/DAFL-artifact/blob/963f46fa147901cbb114be7aecb8f4fc375ae941/scripts/benchmark.py#L24

null1024-ws commented 7 months ago

Thanks for pointing out my mistake.