Skip to content

Commit

Permalink
chore: fix typo (#1368)
Browse files Browse the repository at this point in the history
Signed-off-by: standstaff <[email protected]>
  • Loading branch information
standstaff authored Dec 9, 2024
1 parent 26ef43d commit 7c52f4a
Showing 1 changed file with 1 addition and 1 deletion.
2 changes: 1 addition & 1 deletion src/forge/traces.md
Original file line number Diff line number Diff line change
Expand Up @@ -47,7 +47,7 @@ Some traces might be harder to grasp at first glance. These include:

- The `OOG` shorthand stands for "Out Of Gas".
- The acronym `EOF` stands for "Ethereum Object Format", which introduces an extensible and versioned container format for EVM bytecode. For more information, read [here](https://evmobjectformat.org/).
- `NotActivated` means the feature or opcode is not activated. Some versions of the EVM only support certain opcodes. You may need to use a more recent version usign the `--evm_version` flag. For example, the `PUSH0` opcode is only available since the [Shanghai](https://www.evm.codes/?fork=shanghai) hardfork.
- `NotActivated` means the feature or opcode is not activated. Some versions of the EVM only support certain opcodes. You may need to use a more recent version using the `--evm_version` flag. For example, the `PUSH0` opcode is only available since the [Shanghai](https://www.evm.codes/?fork=shanghai) hardfork.
- `InvalidFEOpcode` means that an undefined bytecode value has been encountered during execution. The EVM catches the unknown bytecode and returns the `INVALID` opcode instead, of value `0xFE`. You can find out more [here](https://www.evm.codes/#fe).

For a deeper insight into the various traces, you can explore the [revm source code](https://github.com/bluealloy/revm/blob/main/crates/interpreter/src/instruction_result.rs).

0 comments on commit 7c52f4a

Please sign in to comment.