You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{"pc":423,"op":"DUP4","gas":317741,"gasCost":3,"depth":1},{"pc":424,"op":"CALL","gas":317738,"gasCost":6740,"depth":1},// <-- should be 6740{"pc":425,"op":"POP","gas":310998,"gasCost":2,"depth":1}
Actual behaviour
{"pc":423,"op":"DUP4","gas":317741,"gasCost":3,"depth":1},{"pc":424,"op":"CALL","gas":317738,"gasCost":9040,"depth":1},// <-- wrong{"pc":425,"op":"POP","gas":310998,"gasCost":2,"depth":1}// <-- funny, the next gas is correct
This is a transaction from a very early block, this was fixed in #18503. It's not in the 1.8-branch, IIRC, but it is fixed on master and will appear in the 1.9 release.
I don't believe it's scheduled for backporting into 1.8, but if it's very important to you we can consider it.... (?)
Thanks for the reply.
I already download and compile master branch of upcoming 1.9.x.
I observed this issue is not addressed yet.
bugfix #18503 only touch the fork choice problem.
I believe #17914 enhancement also infected by this issue because the problem lies in the EVM, not in the tracer.
in opcode CALL, CALLCODE, STATICCALL, DELEGATECALL, and CREATE, the tracer seems ignoring returnGas and only take into account gasCost before opcode execution.
System information
Expected behaviour
Actual behaviour
Steps to reproduce the behaviour
we are developing EVM debugging tools that depend on geth's debugging caps, but turn out we also found bug in geth
debug_traceTransaction
.The text was updated successfully, but these errors were encountered: