Some AFL UI example fuzzer cleanup (#1529)

* Some afl ui cleanup

* more info

* Fix CI (#1549)

* Change profiles for the fuzzbench fuzzers.

* just foreground

* Revert "just foreground"

This reverts commit abd4fbe.

* fix Makefile.toml

* Tmate debug

* fix?

* fix?

* Can't fix this

* remove reset

---------

Co-authored-by: Dongjia "toka" Zhang <[email protected]>

Author: domenukk

fuzzers/libfuzzer_libpng_AFLStyle_UI/.gitignore renamed to fuzzers/libfuzzer_libpng_aflpp_ui/.gitignore

@@ -159,26 +159,19 @@ windows_alias = "unsupported"
 script_runner = "@shell"
 script='''
 rm -rf libafl_unix_shmem_server || true
-(timeout 11s ./${FUZZER_NAME} >/dev/null 2>/dev/null || true) &
+(timeout --foreground 11s ./${FUZZER_NAME} >/dev/null 2>/dev/null || true) &
 sleep 0.2
-timeout 10s ./${FUZZER_NAME} >/dev/null 2>/dev/null || true
-cd ./corpus
-if [ $(ls -al |grep "^-"|wc -l) -gt 4 ]; then
-    echo "Fuzzer is working"
-else
-    echo "Fuzzer does not generate any testcases or any crashes"
-    exit 1
-fi
+timeout --foreground 10s ./${FUZZER_NAME} >/dev/null 2>/dev/null || true
 '''
 dependencies = [ "fuzzer" ]
 
 [tasks.test_mac]
 script_runner = "@shell"
 script='''
 rm -rf libafl_unix_shmem_server || true
-(timeout 11s ./${FUZZER_NAME} >fuzz_stdout.log 2>/dev/null || true) &
+(timeout --foreground 11s ./${FUZZER_NAME} >fuzz_stdout.log 2>/dev/null || true) &
 sleep 0.2
-timeout 10s ./${FUZZER_NAME} >/dev/null 2>/dev/null || true
+timeout --foreground 10s ./${FUZZER_NAME} >/dev/null 2>/dev/null || true
 '''
 dependencies = [ "fuzzer" ]
 

fuzzers/libfuzzer_libpng_AFLStyle_UI/Cargo.toml renamed to fuzzers/libfuzzer_libpng_aflpp_ui/Cargo.toml

@@ -1,15 +1,8 @@
-# Libfuzzer for libpng
+# Libfuzzer for libpng, with AFL-style UI
 
 This folder contains an example fuzzer for libpng, using LLMP for fast multi-process fuzzing and crash detection.
 
-In contrast to other fuzzer examples, this setup uses `fuzz_loop_for`, to occasionally respawn the fuzzer executor.
-While this costs performance, it can be useful for targets with memory leaks or other instabilities.
-If your target is really instable, however, consider exchanging the `InProcessExecutor` for a `ForkserverExecutor` instead.
-
-It also uses the `introspection` feature, printing fuzzer stats during execution.
-
-To show off crash detection, we added a `ud2` instruction to the harness, edit harness.cc if you want a non-crashing example.
-It has been tested on Linux.
+In contrast to other fuzzer examples, it keeps track of AFL style metrics and display them in the terminal.
 
 ## Build