You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
You have verified that the issue to be present in the current main branch
Yes
# git log | head -n 1
commit 27677a64616df5d7fb0f8c87baa91fb775045725
Describe the bug
similar to #2579 I get an error about restarting when I use the following harness with the qemu_launcher example fuzzer. I have tried this with and without the --privileged flag from a docker stand point.
To Reproduce
The setup of the docker file / build of the fuzzer is the same as in #2579 and then running the qemu_launcher example fuzzer with the harness above.
# cd fuzzers/binary_only/qemu_launcher/ && cargo make build
SNIP
# cd target/x86_64/
# nano harness.c
# <paste in the harness above>
# gcc -o harness ./harness.c
# mkdir -p in && echo AAAAAAAAAA > in/a
# ./release/qemu_launcher --verbose --cores 0 --input in --output out -- ./harness
[UserStats #1] (GLOBAL) run time: 0h-0m-0s, clients: 1, corpus: 0, objectives: 0, executions: 0, exec/sec: 0.000, edges: 100.000%
(CLIENT) corpus: 0, objectives: 0, executions: 0, exec/sec: 0.000, edges: 2/2 (100%)
[Testcase #1] (GLOBAL) run time: 0h-0m-0s, clients: 1, corpus: 1, objectives: 0, executions: 0, exec/sec: 0.000, edges: 100.000%
(CLIENT) corpus: 1, objectives: 0, executions: 0, exec/sec: 0.000, edges: 2/2 (100%)
We imported 1 inputs from disk.
qemu: uncaught target signal 6 (Aborted) - core dumped
thread 'main' panicked at /tmp/LibAFL/libafl/src/events/llmp/restarting.rs:637:21:
Fuzzer-respawner: Storing state in crashed fuzzer instance did not work, no point to spawn the next client! This can happen if the child calls `exit()`, in that case make sure it uses `abort()`, if it got killed unrecoverable (OOM), or if there is a bug in the fuzzer itself. (Child exited with: 0)
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace
Fuzzing stopped by user. Good bye.
Expected behavior
Per the error message, I would assume that the fuzzer would restart the core as this harness calls abort() rather than exit().
main
branchYes
Describe the bug
similar to #2579 I get an error about restarting when I use the following harness with the qemu_launcher example fuzzer. I have tried this with and without the
--privileged
flag from a docker stand point.To Reproduce
The setup of the docker file / build of the fuzzer is the same as in #2579 and then running the qemu_launcher example fuzzer with the harness above.
Expected behavior
Per the error message, I would assume that the fuzzer would restart the core as this harness calls
abort()
rather thanexit()
.Additional context
Environment info
Full stack trace with
RUST_BACKTRACE=full
is below.The text was updated successfully, but these errors were encountered: