bsc/eth/tracers
Delweng 8e69622c68
eth/tracers: add withLog to callTracer (#25991)
In some cases, it is desirable to capture what is triggered by each trace, when using the `callTracer`. For example: call `USDT.transfer` will trigger a `Transfer(from, to, value)` event.

This PR adds the option to capture logs to the call tracer, by specifying `{"withLog": true}` in the tracerconfig. 
Any logs belonging to failed/reverted call-scopes are removed from the output, to prevent interpretation mistakes.

Signed-off-by: Delweng <delweng@gmail.com>
Co-authored-by: Sina Mahmoodi <itz.s1na@gmail.com>
2022-11-01 12:03:26 +01:00
..
internal/tracetest eth/tracers: add withLog to callTracer (#25991) 2022-11-01 12:03:26 +01:00
js eth/tracers: fix gasUsed for native and JS tracers (#26048) 2022-10-28 12:28:29 +02:00
logger core, eth: pre-allocate map in storage copy (#25279) 2022-07-12 10:08:45 +03:00
native eth/tracers: add withLog to callTracer (#25991) 2022-11-01 12:03:26 +01:00
api_test.go core, ethclient/gethclient: improve flaky tests (#25918) 2022-10-06 13:39:20 +02:00
api.go eth/traces: add state limit (#25812) 2022-10-06 10:48:04 +02:00
tracers_test.go all: more linters (#24783) 2022-06-13 16:24:45 +02:00
tracers.go eth/tracers: add onlyTopCall option to callTracer (#25430) 2022-08-09 11:04:57 +02:00
tracker_test.go eth/traces: add state limit (#25812) 2022-10-06 10:48:04 +02:00
tracker.go eth/traces: add state limit (#25812) 2022-10-06 10:48:04 +02:00