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.

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

Allow echidna to pin to specific system variables, and only show the value of those variables after each failed call sequence #1214

Open
0xicingdeath opened this issue Mar 12, 2024 · 0 comments

Comments

@0xicingdeath
Copy link
Contributor

Describe the desired feature

Once a contract emits an event, in many cases it will emit intermediate values / adjusted values, etc – and it would be really handy to be able to see this output from the fuzzer for the entire call of sequences (and not just the last one that resulted in the failure).

We've seen quite a few issues historically that have resulted in 5-6 sequences (or more, up to 90 and change 😛), where the bug wasn't in the function that was being called in the last assertion, but was actually introduced in say, transaction 3 or 4, and required us to dig into the system to understand what its impact was on other invariants. Having the event traces and visibility into the arguments for those events would be useful to help make debugging a little easier.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant