Fuzzing failed: Empty("No entries in corpus", ErrorBacktrace)
0xxfu opened this issue · comments
Command:
RUST_BACKTRACE=full ityfuzz evm\
-t 0x6EDd21f5e3B77b1C42cacD8b724Ef139a06521DC\
-o -i -f -c MUMBAI\
--onchain-block-number 42468364\
--onchain-etherscan-api-key ${privateKey}
Print:
================ EVM Fuzzer Start ===================
INFO Deploying contract: 0x6edd21f5e3b77b1c42cacd8b724ef139a06521dc
INFO Contract 0x6edd21f5e3b77b1c42cacd8b724ef139a06521dc deployed to: 0x6edd21f5e3b77b1c42cacd8b724ef139a06521dc
INFO Deployed all contracts
thread 'main' panicked at src/fuzzers/evm_fuzzer.rs:615:18:
Fuzzing failed: Empty("No entries in corpus", ErrorBacktrace)
stack backtrace:
0: 0x1044c939c - <std::sys_common::backtrace::_print::DisplayBacktrace as core::fmt::Display>::fmt::hdcf5a8f170d2fa38
1: 0x1044e940c - core::fmt::write::h43a20d1d43ba2c4c
2: 0x1044c6434 - std::io::Write::write_fmt::hc8f02cc7d187633a
3: 0x1044c91d8 - std::sys_common::backtrace::print::h0f98126c99b558bc
4: 0x1044caafc - std::panicking::default_hook::{{closure}}::h37ce2903b5a4a707
5: 0x1044ca844 - std::panicking::default_hook::hdce48845581ed2b0
6: 0x1044cb05c - std::panicking::rust_panic_with_hook::h130fbf332c6cdd6d
7: 0x1044cae24 - std::panicking::begin_panic_handler::{{closure}}::hace05675132c4b37
8: 0x1044c9804 - std::sys_common::backtrace::__rust_end_short_backtrace::hb5df50aeda7bb9d6
9: 0x1044cabc0 - _rust_begin_unwind
10: 0x104542900 - core::panicking::panic_fmt::h9d18abbacad43fc7
11: 0x104542ca0 - core::result::unwrap_failed::h1982ddb351d8116e
12: 0x1031b1f0c - ityfuzz::fuzzers::evm_fuzzer::evm_fuzzer::hd4f4447089792720
13: 0x10316732c - ityfuzz::evm::evm_main::h1237508dee5fb77c
14: 0x103013c90 - ityfuzz::main::h9b6e035e457fa007
15: 0x1031438e8 - std::sys_common::backtrace::__rust_begin_short_backtrace::h12c2fff17dffdd36
16: 0x1030720c0 - std::rt::lang_start::{{closure}}::he6aa290337ebd73f
17: 0x1044bfd5c - std::rt::lang_start_internal::hb81d8036ff3fc9c3
18: 0x1030720a4 - std::rt::lang_start::h4bc7fc1d757e5f18
19: 0x10301507c - _main
This problem is due to the built-in RPC not getting the bytecode.
To solve:
export ETH_RPC_URL=https:/ your.mumbai . rpc
ityfuzz evm\
-t 0x6EDd21f5e3B77b1C42cacD8b724Ef139a06521DC\
-o -i -f -c MUMBAI\
--onchain-block-number 42468364\
--onchain-etherscan-api-key ${privateKey}
Can error prompts be friendlier? The error above seems to have nothing to do with RPC.
Okay, thank you. It works for me after setting up RPC.
