display solidity source of current PC and bytecode if execution reverts during deployment

crytic / medusa

Parallelized, coverage-guided, mutational Solidity smart contract fuzzing, powered by go-ethereum

https://www.trailofbits.com/

GNU Affero General Public License v3.0

273 stars 33 forks source link

display solidity source of current PC and bytecode if execution reverts during deployment #320

Open 0xalpharush opened 3 months ago

0xalpharush commented 3 months ago

If a contract reverts in the constructor during the initial deployment, it'd be helpful to provide the user more context such as the decoded error or message in the require statement. Ideally the source line that caused it.

Currently we just get: ‣ contract deployment tx returned a failed status: execution reverted

0xalpharush commented 3 months ago

It would also be nice to show the source line for assertion failure traces [panic: assertion failed] -> [panic: assertion failed] at fuzz.sol:1337