This question already has an answer here:
- What does a “bad JUMPDEST” error mean? 2 answers
There are a number of questions relating to the
invalid JUMP error.
I get this when debugging a solidiy contract on the testrpc with geth command line:
Error: VM Exception while processing transaction: invalid JUMP at 3802e3b6eefb98 150918c4ddfaabf93c18d6c41aaa2682c5cdbc0a9a9a6a2853/cb611bab0cd7c4f21f7cb0b91ad45 f1330995289:13717 at web3.js:3119:20 at web3.js:6023:15 at web3.js:4995:36 at web3.js:4055:16 at apply (<native code>) at web3.js:4141:16 at <anonymous>:1:1
Can you explain the invlid JUMP error - what is going wrong at the Virtual Machine opcode level?
What approach should you use when finding the source of such errors?
Is this error unique to go-ethereum?
The question is answered here:
What is the distinction, if any, between the above
invlaid JUMP and that question's