We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Hi, I'm curious how we can use it for our Move module.
I try to set the config and pointing to my move module.
make CONFIG_PATH="./config.json" TARGET_MODULE="sui_gives" TARGET_FUNCTION="create_locker_contents"
But it is not working and show the following error:
warning: `fuzzer` (bin "fuzzer") generated 1 warning (run `cargo fix --bin "fuzzer"` to apply 1 suggestion) Finished release [optimized] target(s) in 1.61s if [ -z "" ]; then \ if [ -z "" ]; then \ cargo run --release -- --config-path ./config.json --target-module fuzzinglabs_module --target-function fuzzinglabs 2> log; \ else \ cargo run --release -- --config-path ./config.json --target-module fuzzinglabs_module --functions 2> log; \ fi \ else \ cargo run --release -- --config-path ./config.json --target-module fuzzinglabs_module --target-function fuzzinglabs --detectors 2> log; \ fi make: *** [Makefile:3: all] Error 101
My config is the following:
{ "use_ui": true, "nb_threads": 2, "seed": 4242, "contract": "/path/to/my/package", "execs_before_cov_update": 10000, "corpus_dir": "./corpus", "crashes_dir": "./crashes", "fuzz_functions_prefix": "fuzz_", "max_call_sequence_size": 5 }
The text was updated successfully, but these errors were encountered:
Hi !
Did you check the log file (the Makefile redirects stderr to a log file) ? You should have more information about your issue in it.
Sorry, something went wrong.
No branches or pull requests
Hi, I'm curious how we can use it for our Move module.
I try to set the config and pointing to my move module.
But it is not working and show the following error:
My config is the following:
The text was updated successfully, but these errors were encountered: