I discovered this first in ethereumjs-vm 1.4 and could reproduce it in 2.0. Strangely this bug is system specific - it lead to a crash on Ubuntu but succeeded on OS X.
The error happens on a deployment of contract A which deploys another contract B. Code was compiled with solidity 0.4.3
At some Point the stack look like the following:
0 0x00b68db15676a4024a0b2cfe93c41c10c2323c44 <- B's address after deployment
1 0x01
...
Here the operation MUL is performed which produces the stack:
0 0xb68db15676a4024a0b2cfe93c41c10c2323c44
...
Note that the new address misses its 00 prefix which later leads to an error.
I discovered this first in ethereumjs-vm 1.4 and could reproduce it in 2.0. Strangely this bug is system specific - it lead to a crash on Ubuntu but succeeded on OS X.
The error happens on a deployment of contract A which deploys another contract B. Code was compiled with solidity 0.4.3
At some Point the stack look like the following:
Here the operation MUL is performed which produces the stack:
Note that the new address misses its 00 prefix which later leads to an error.