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.

Sign up for GitHub

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

Jump to bottom

every EVM opcode has potential to OOG and ruin tracing result #244

Closed
jangko opened this issue Feb 25, 2019 · 0 comments
Closed

every EVM opcode has potential to OOG and ruin tracing result #244

jangko opened this issue Feb 25, 2019 · 0 comments

Comments

@jangko
Copy link
Contributor

jangko commented Feb 25, 2019 •
edited by 0xc1c4da
Loading

current implementation:
If an opcode trigger OOG, it will raise exception, there is no chance for the tracer to record the gas consumption.

The problem become worse if the computation have more than one depth. There will be many opcode with blank gasCost field in the tracing result.

Besides making EVM debugging more difficult, the incorrect tracing result also does not conform to the standard tracing result.

example block: 420301
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@jangko