You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
t8n is supposed to produce vmtrace files in out directory
Trace file `trace-0-0xeda4d6763740fbccc99cc8873ff09b8504d192e83f73bd16ccf5feb053a4e3cd.jsonl` not found!
WARNING: Transaction trace not found! (0xeda4d6763740fbccc99cc8873ff09b8504d192e83f73bd16ccf5feb053a4e3cd)
trace-[txIndex]-[txHash].jsonl
t8n trace options:
--trace (default: false)
Output full trace logs to files <txhash>.jsonl
--trace.memory (default: false)
Enable full memory dump in traces
--trace.nomemory (default: true)
Disable full memory dump in traces (deprecated)
--trace.noreturndata (default: true)
Disable return data output in traces (deprecated)
--trace.nostack (default: false)
Disable stack output in traces
--trace.returndata (default: false)
Enable return data output in traces
the trace format must be exactly the same as of issue: ethereum/tests#249
but better to compare to the outputs produced by geth.
if we have the same trace format we can use tools to find transaction execution bugs
The text was updated successfully, but these errors were encountered:
we have gasPrice disagreement on nimbus vs geth on this test ethereum/go-ethereum#27721 (opcodeBlobhashOutOfRangeFiller.yml)
would be nice to see nimbus vm trace to compare it with geth
geth vmtrace format:
t8n is supposed to produce vmtrace files in out directory
trace-[txIndex]-[txHash].jsonl
t8n trace options:
the trace format must be exactly the same as of issue: ethereum/tests#249
but better to compare to the outputs produced by geth.
if we have the same trace format we can use tools to find transaction execution bugs
The text was updated successfully, but these errors were encountered: