Has the stack of the caller / creator been updated to contain the `successBit` / `deploymentAddress` (or `0`) at `TraceContextReEntry` ?
Opened this issue · 1 comments
OlivierBBB commented
Empirically this is the case for CALL's. We (@letypequividelespoubelles and @OlivierBBB) didn't (yet) investigate for CREATE's.
@daniellehrner & @lu-pinto could you please confirm the above ?
lu-pinto commented
I think this even happens upon traceContextExit
on the child's frame. Check here when the complete
handle method for the child is called just after traceContextExit
.
For CREATE both contract address and result occur at the same time as above in CALL right about here.