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
Command: FUZZCHECK_ARGS="my test" MIRIFLAGS=-Zmiri-disable-isolation cargo +miri2 miri run
Environment: Linux G22L059 5.19.0-50-generic #50-Ubuntu SMP PREEMPT_DYNAMIC Mon Jul 10 18:24:29 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux
Error 1: I got the following error when trying to execute the above command using my custom Rustc toolchain (named miri2)."
thread 'main' panicked at 'could not find all relevant LLVM coverage sections: CannotFindSection { section: CovMap }', /home/y23kim/rust/fuzzcheck-rs/fuzzcheck/src/code_coverage_sensor/mod.rs:55:57
Error 2: When I modified this part(/home/y23kim/rust/fuzzcheck-rs/fuzzcheck/src/code_coverage_sensor/mod.rs:55:57) to return an empty CoverageSensor struct, above error was disappeared but another error occurred.
error: unsupported operation: can't call foreign function `sigaltstack` on OS `linux`
--> /home/y23kim/rust/fuzzcheck-rs/fuzzcheck/src/signals_handler.rs:46:17
|
46 | let stack = libc::sigaltstack(&signal_stack, std::ptr::null_mut());
| ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ can't call foreign function `sigaltstack` on OS `linux`
|
= help: this is likely not a bug in the program; it indicates that the program performed an operation that the interpreter does not support
Are these two errors caused by using my custom RustC and MIRI Toolchain? The second one seems like an obvious bug, but I'm unable to speculate on the cause of the first one.
Error 1 probably originates from not compiling your program with coverage counters enabled. You can either use cargo fuzzcheck or set the RUSTFLAGS=-C instrument-coverage environment variable to fix this.
I'm not really sure about Error 2, but my guess is that this may be a MIRI-specific issue (as the sigaltstack syscall may cause the interpreter some problems). Can you try running your program without using MIRI and see if the issue persists?
Even if MIRI doesn't work with Fuzzcheck, LLVM's santizers should work (other people have been able to use them without issue). Perhaps ASAN/MSAN might work for your use-case?
FUZZCHECK_ARGS="my test" MIRIFLAGS=-Zmiri-disable-isolation cargo +miri2 miri run
Linux G22L059 5.19.0-50-generic #50-Ubuntu SMP PREEMPT_DYNAMIC Mon Jul 10 18:24:29 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux
/home/y23kim/rust/fuzzcheck-rs/fuzzcheck/src/code_coverage_sensor/mod.rs:55:57
) to return an empty CoverageSensor struct, above error was disappeared but another error occurred.Are these two errors caused by using my custom RustC and MIRI Toolchain? The second one seems like an obvious bug, but I'm unable to speculate on the cause of the first one.
I attached my main function for your information.
The text was updated successfully, but these errors were encountered: