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.

Sign up for GitHub

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

Jump to bottom

Add a recommendation to solve VM failed for unhandled reason, MaxInitCodeSizeExceeded #355

Open
wants to merge 1 commit into
base: master
Choose a base branch
from
Open

Add a recommendation to solve VM failed for unhandled reason, MaxInitCodeSizeExceeded #355

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 4 additions & 0 deletions program-analysis/echidna/frequently_asked_questions.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -2,6 +2,10 @@

This list provides answers to frequently asked questions related to the usage of Echidna. If you find this information challenging to understand, please ensure you have already reviewed [all the other Echidna documentation](./README.md).

## Echidna fails to start saying `VM failed for unhandled reason, MaxInitCodeSizeExceeded`

One or more contracts that you try to deploy are too big for the EVM. However, this can be easy solved from inside Echidna adding `codeSize: 0xffffffff` into your config file. Keep in mind that the contracts that you are using will *fail* to deploy on the real EVM, so they should only be used for testing.

## Echidna fails to start or compile my contract; what should I do?

Begin by testing if `crytic-compile` can compile your contracts. If you are using a compilation framework such as Truffle or Hardhat, use the command:
Expand Down
Loading