Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

thread 'fuzzer_1' panicked at 'couldn't read child hello #27

Open
qijiale opened this issue Nov 22, 2022 · 2 comments
Open

thread 'fuzzer_1' panicked at 'couldn't read child hello #27

qijiale opened this issue Nov 22, 2022 · 2 comments

Comments

@qijiale
Copy link

qijiale commented Nov 22, 2022

When i run 'cargo run ../AFLplusplus/afl-qemu-trace -- ./main @@', it's fail.

Finished dev [unoptimized + debuginfo] target(s) in 0.04s
Running target/debug/fuzzer ../AFLplusplus/afl-qemu-trace -- ./main '@@'
[2022-11-22] 08:13:05 Starting Fuzzing...
thread 'fuzzer_1' panicked at 'couldn't read child hello: Error { kind: UnexpectedEof, message: "failed to fill whole buffer" }', forksrv/src/lib.rs:98:22.

What should I address it?

@1013503897
Copy link

verify if your binary file has been instrumented correctly with AFL++

@extf33
Copy link

extf33 commented May 31, 2023

verify if your binary file has been instrumented correctly with AFL++

Why it panics if binary file hasn't instrumented correctly by AFL++? I read the code, but I don't understand it well,

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants