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

Question: tracing #61

Closed
revitteth opened this issue Sep 19, 2022 · 3 comments
Closed

Question: tracing #61

revitteth opened this issue Sep 19, 2022 · 3 comments

Comments

@revitteth
Copy link

Tracing appears to be a highly useful but delicate area of the client ecosystem, would it be possible to add some tracing to the fuzzer?

@holiman
Copy link
Owner

holiman commented Sep 19, 2022

Well... The fuzzer is really based on tracing, not sure exactly what you mean. After the fuzzer finds an interesting case, it emits the trace-files, which can be investigated manually (or by tracediff/traceview). Don't know what else to do .. ?

@revitteth
Copy link
Author

Sure, sorry I think I've got some specific cases which we could include which may show some issues tracing transactions/blocks with specific properties.

For example this tx on etherscan (state change tab shows no data): https://etherscan.io/tx/0x2fdf04a1d70c3cfa1f9d89baf080377ca110c5dbc28def63b01e18b270e85f6f#statechange

There is a full discussion here: erigontech/erigon#5306 and it looks like this potentially affects multiple clients.

@holiman
Copy link
Owner

holiman commented Dec 3, 2022

This is unrelated to goevmlab

@holiman holiman closed this as completed Dec 3, 2022
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

No branches or pull requests

2 participants