Marko Veniger
Marko Veniger
@ekpyron This is what I mentioned in our chat, it should be reproducible from this
note: there could be considerations that this optimization could make an execution diff if the stack had no items on it prior to the ```PUSH0``` instruction, where without the optimization...
I can take over this PR and issue and start working on it next week
I can take over this PR and issue and start working on it next week
This topic requires additional discussion, particularly on finding ways of representing parts of code that are affected by inline functions and identifying ways to calculate arguments to the function being...
This issue is partially blocked by [ethdebug/format#139](https://github.com/ethdebug/format/issues/139), but the implementation can be started
Note: Support level equivalent to Source Maps means not including multiple source locations for instructions that have been affected by deduplication. This will be possible when the (partially) blocking issue...
This issue has been created to track high level progress on this feature implementation, sub-issues will be created for specific tasks if needed /cc @aarlt @ekpyron
In order to slim down the size of debug data, context should be changed to stateful instead of tracing each variable on each instruction by having variables enter or leave...
The deduplication issue as defined in #139 should be resolved for this issue also