Skip to content
This repository has been archived by the owner on Feb 26, 2024. It is now read-only.

Problem with stacktraces and optimized code in Solidity 0.8.x #3876

Open
haltman-at opened this issue Feb 25, 2021 · 0 comments
Open

Problem with stacktraces and optimized code in Solidity 0.8.x #3876

haltman-at opened this issue Feb 25, 2021 · 0 comments

Comments

@haltman-at
Copy link
Contributor

haltman-at commented Feb 25, 2021

Issue

See this Brownie PR; we're also going to need a fix for this.

Basically, with Solidity 0.8.x, if optimization is turned on, all reverts will appear to be the same revert, which may mess up stacktraces. So, we may want something where in this case we effectively treat that code that maps to reverts as unmapped instead...?

Environment

  • Truffle version (truffle version): 5.1.67
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

2 participants