bb3651abc8
Consensus rules dictate that objects can only be removed during the finalisation of the transaction (i.e. after all calls have finished). Thus calling a suicided contract twice from the same transaction: A->B(S)->ret(A)->B(S) results in 2 suicides. Calling the suicided object twice from two transactions: A->B(S), A->B, results in only one suicide and a call to an empty object. Our current debug tracing functionality replays all transaction that were executed prior to the targetted transaction in order to provide the user with an accurate trace. As a side effect to calling StateDB.IntermediateRoot it also deletes any suicides objects. Our tracing code never calls this function because it isn't interested in the intermediate root. Becasue of this it caused a bug in the tracing code where transactions that were send to priviously deleted objects resulted in two suicides rather than one suicide and a call to an empty object. Fixes #2542 |
||
|---|---|---|
| .. | ||
| dump.go | ||
| iterator_test.go | ||
| iterator.go | ||
| main_test.go | ||
| managed_state_test.go | ||
| managed_state.go | ||
| state_object.go | ||
| state_test.go | ||
| statedb_test.go | ||
| statedb.go | ||
| sync_test.go | ||
| sync.go | ||