Skip to content

Conversation

@patrick-ogrady
Copy link
Contributor

@patrick-ogrady patrick-ogrady commented Feb 5, 2021

Related: ava-labs/avalanchego#752

debug_traceTransaction will panic when tracing transactions (with this script) that deploy contracts with no code. This was discovered when tracing 0xc0f33007b76c2d8675cdc34e979b94f3aab4778572be0b185115bbd4686f6a17 on FUJI.

The root cause of this issue is that the dbWrapper.db is not populated in the tracer when a transaction contains a lone contract deployment that has no code. result (called at the end of debug_traceTransaction assumes this wrapper was populated with StateDB at some point.

@patrick-ogrady patrick-ogrady changed the title [Tracer] Handle Empty Contract Deployments [WIP] [Tracer] Handle Empty Contract Deployments Feb 5, 2021
@patrick-ogrady patrick-ogrady force-pushed the empty-contract-trace-error branch from ceebd7c to bed852b Compare February 6, 2021 00:05
@patrick-ogrady patrick-ogrady changed the title [WIP] [Tracer] Handle Empty Contract Deployments [Tracer] Handle Empty Contract Deployments Feb 6, 2021
@patrick-ogrady
Copy link
Contributor Author

Waiting on upstream PR to confirm this is the best approach to fix this: ethereum/go-ethereum#22276

@aaronbuchwald aaronbuchwald changed the base branch from master to dev February 7, 2021 17:05
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