[Tracer] Handle Empty Contract Deployments #98
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Related: ava-labs/avalanchego#752
debug_traceTransactionwill panic when tracing transactions (with this script) that deploy contracts with no code. This was discovered when tracing0xc0f33007b76c2d8675cdc34e979b94f3aab4778572be0b185115bbd4686f6a17onFUJI.The root cause of this issue is that the
dbWrapper.dbis not populated in the tracer when a transaction contains a lone contract deployment that has no code.result(called at the end ofdebug_traceTransactionassumes this wrapper was populated withStateDBat some point.