This repository has been archived by the owner on Oct 28, 2021. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 2.2k
Different behaviours between parity-evm and aleth-vm #5880
Comments
BTW, the output is: {"output": "", "gasUsed": "0x7fffffffffffffff"}
I want to figured out why the gasUsed is 0x7fffffffffffffff? As describe above, the trace has only one operation "MOD", I'm also very confused by the result of trace. If you can give me some nice explanations, many thanks:) |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Parity Ethereum version: the newest one
Operating system: Linux(ubuntu16.04)
Installation: built from source
Fully synchronized: no
Aleth Ethereum version: the newest one
Operating system: Linux(ubuntu16.04)
Installation: built from source
Fully synchronized: no
steps to reproduce
import subprocess
actual behavior
Invalid --code: Invalid input length
255
[
{
"depth" : "0",
"gas" : "9223372036854775807",
"gasCost" : "0",
"memory" : [],
"op" : "MOD",
"pc" : "0",
"stack" : [],
"storage" : {}
}
]
0
expected bahaviour
should be the same
I want to figure what's the meaning of Invalid input length? and why aleth-vm can run the bin-runtime code normally(retcode is 0) and the parity-evm run the same bin-runtime code with error(retcode is 255)? Many thanks:)
The text was updated successfully, but these errors were encountered: