Fuzz end but no crash file generated

[cokeBeer]

Describe the bug Run bady_fuzzer.py, fuzz end but no crash file generated.

To Reproduce Steps to reproduce the behavior:

1. run bady_fuzzer.py

Expected behavior Crash file generated

Screen output/Screenshots

Additional context No crash file found in crash directory. Seems only happens on Windows system

[SpaceWhite]

Hi @cokeBeer I couldn't reproduce the issue above. crash files are created on the directory Could you provide more details such as python version, OS version, libafl version, etc?

Here is what I have done to reproduce the issue

(.env) user@DESKTOP-AC0CQLQ:~/libafl/fuzzers/baby_fuzzer$ ls
Cargo.lock  Cargo.toml  README.md  baby_fuzzer.py  src  target
(.env) user@DESKTOP-AC0CQLQ:~/libafl/fuzzers/baby_fuzzer$ python3 baby_fuzzer.py
[Stats #0] run time: 0h-0m-0s, clients: 1, corpus: 0, objectives: 0, executions: 0, exec/sec: 0.000
[Testcase #0] run time: 0h-0m-0s, clients: 1, corpus: 1, objectives: 0, executions: 1, exec/sec: 0.000
[Stats #0] run time: 0h-0m-0s, clients: 1, corpus: 1, objectives: 0, executions: 1, exec/sec: 0.000
[Testcase #0] run time: 0h-0m-0s, clients: 1, corpus: 2, objectives: 0, executions: 20, exec/sec: 0.000
thread '<unnamed>' panicked at 'called `Result::unwrap()` on an `Err` value: PyErr { type: <class 'Exception'>, value: Exception('NOOOOOO =)'), traceback: Some(<traceback object at 0x7fcb3e0abec0>) }', /home/user/libafl/libafl/src/executors/inprocess.rs:2151:26
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace
[Objective #0] run time: 0h-0m-0s, clients: 1, corpus: 2, objectives: 1, executions: 20, exec/sec: 0.000
INFO:libafl.executors.inprocess:Waiting for broker...
INFO:libafl.executors.inprocess:Bye!
(.env) user@DESKTOP-AC0CQLQ:~/libafl/fuzzers/baby_fuzzer$ ls -lah
total 60K
drwxrwxr-x  5 user user 4.0K Mar 12 15:50 .
drwxrwxr-x 45 user user 4.0K Mar  7 10:53 ..
-rw-rw-r--  1 user user    8 Mar  7 10:53 .gitignore
-rw-rw-r--  1 user user  23K Mar  7 10:56 Cargo.lock
-rw-rw-r--  1 user user  383 Mar  7 10:53 Cargo.toml
-rw-rw-r--  1 user user  310 Mar  7 10:53 README.md
-rw-rw-r--  1 user user 2.9K Mar  7 10:53 baby_fuzzer.py
drwxrwxr-x  2 user user 4.0K Mar 12 15:50 crashes
drwxrwxr-x  2 user user 4.0K Mar 12 15:45 src
drwxrwxr-x  3 user user 4.0K Mar  7 10:56 target
(.env) user@DESKTOP-AC0CQLQ:~/libafl/fuzzers/baby_fuzzer$ ls -alh crashes
total 16K
drwxrwxr-x 2 user user 4.0K Mar 12 15:50 .
drwxrwxr-x 5 user user 4.0K Mar 12 15:50 ..
-rw-rw-r-- 1 user user    0 Mar 12 15:50 .484bec814b4e5372.lafl_lock
-rw-rw-r-- 1 user user  166 Mar 12 15:50 .484bec814b4e5372.metadata
-rw-rw-r-- 1 user user   19 Mar 12 15:50 484bec814b4e5372

Tested environment

OS : Windows 10 pro 19044.2604 
WSL :  Ubuntu 20.04 TLS
cargo : 1.67.1 (8ecd4f20a 2023-01-10)
rustc : 1.67.1 

[cokeBeer]

@SpaceWhite Windows 10 10.0.19045, libafl latest commit, cargo 1.67.1 (8ecd4f20a 2023-01-10), rustc 1.67.1. Just clone LibAFL, run maturin develop, and run baby_fuzzer.py. I am not using WSL. I use powershell.

[domenukk]

I think nobody has Windows right now so we'll need help here

[tokatoka]

i guess this is just because our crash handler not called. from rust panic