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.

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

fix(tracing/builder): ensure the selfdestruct trace is at the ending of the same depth #192

Merged
merged 4 commits into from
Sep 9, 2024

Conversation

jsvisa
Copy link
Contributor

@jsvisa jsvisa commented Sep 9, 2024

because the selfdestruct doesn't have separate trace, if will returned just after the original call, this is inaccure, and we should keep them staying at the ending of the same call depth.

Signed-off-by: jsvisa <delweng@gmail.com>
Signed-off-by: jsvisa <delweng@gmail.com>
Signed-off-by: jsvisa <delweng@gmail.com>
@mattsse mattsse merged commit 4aea842 into paradigmxyz:main Sep 9, 2024
5 of 11 checks passed
@jsvisa jsvisa deleted the suicide-order branch September 9, 2024 16:16
lwedge99 pushed a commit to sentioxyz/revm-inspectors that referenced this pull request Oct 8, 2024
…of the same depth (paradigmxyz#192)

because the selfdestruct doesn't have separate trace, if will returned
just after the original call, this is inaccure, and we should keep them
staying at the ending of the same call depth.

---------

Signed-off-by: jsvisa <delweng@gmail.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants