lightclient dbc1d04f5e core/vm/runtime: ensure tracer benchmark calls OnTxStart (#30257) ... The struct-based tracing added in #29189 seems to have caused an issue with the benchmark `BenchmarkTracerStepVsCallFrame`. On master we see the following panic: ```console BenchmarkTracerStepVsCallFrame panic: runtime error: invalid memory address or nil pointer dereference [signal SIGSEGV: segmentation violation code=0x2 addr=0x40 pc=0x1019782f0] goroutine 37 [running]: github.com/ethereum/go-ethereum/eth/tracers/js.(*jsTracer).OnOpcode(0x140004c4000, 0x0, 0x10?, 0x989680, 0x1, {0x101ea2298, 0x1400000e258}, {0x1400000e258?, 0x14000155928?, 0x10173020c?}, ...) /Users/matt/dev/go-ethereum/eth/tracers/js/goja.go:328 +0x140 github.com/ethereum/go-ethereum/core/vm.(*EVMInterpreter).Run(0x14000307da0, 0x140003cc0d0, {0x0, 0x0, 0x0}, 0x0) ... FAIL github.com/ethereum/go-ethereum/core/vm/runtime 0.420s FAIL ``` The issue seems to be that `OnOpcode` expects that `OnTxStart` has already been called to initialize the `env` value in the tracer. The JS tracer uses it in `OnOpcode` for the `GetRefund()` method. This patch resolves the issue by reusing the `Call` method already defined in `runtime_test.go` which correctly calls `OnTxStart`.		2024-08-06 19:51:48 +08:00
..
doc.go	core/vm/runtime: added simple execution runtime	2015-11-18 16:50:20 +01:00
env.go	core/vm: set basefee to 0 internally on eth_call (#28470)	2023-11-08 11:22:08 +02:00
runtime.go	core/vm/runtime: set random to enable merge-opcodes (#29799)	2024-05-28 13:45:16 +02:00
runtime_example_test.go	core/vm/runtime: added simple execution runtime	2015-11-18 16:50:20 +01:00
runtime_fuzz_test.go	tests/fuzzers: move fuzzers into native packages (#28467)	2023-11-14 14:34:29 +01:00
runtime_test.go	core/vm/runtime: ensure tracer benchmark calls OnTxStart (#30257)	2024-08-06 19:51:48 +08:00