Add printing of OPCODEs in forge tests #8198
Labels
Milestone
Comments
mattsse
pushed a commit
to paradigmxyz/revm-inspectors
that referenced
this issue
Jul 2, 2024
ref foundry-rs/foundry#8222 ref foundry-rs/foundry#8198 Adds structs and extends `TraceWriter` to support formatting of decoded trace steps. Currently two decoding formats are supported: - Internal calls. Similar to a decoded call trace, decoded internal function invocation which spans over multiple steps. Kept as decoded function name, inputs, outputs and index of the last step. - Arbitrary strings. This might be useful for formatting decoded opcodes (e.g. adding `├─ [sload] <slot>` to trace. It might make sense to extend it to something more configurable once we start implementing this
|
I think the current state of this is that the renderer has support for rendering OPCODEs (added in paradigmxyz/revm-inspectors#157) but we still require an implementation of it here that passes to the renderer, correct @klkvr? |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Component
Forge
Describe the feature you would like
One feature that is missing in the tooling would be to print the opcodes that re hit when testing contracts.
For example https://github.com/zemse/hardhat-tracer has the option for you to set if you want to print SLOADs, MLOADs and other OPCODES when testing and also their gas usage. This would be beneficial of gas analysis & gas optimizations.
I know with the debugger you can see the opcodes but its hard to navigate and you can't filter only specific opcodes there
This maybe can be added as a verbosity level 6 or another way where you can specify which opcodes you want printed.
Additional context
No response
The text was updated successfully, but these errors were encountered: