LegacyVM with optimizations reports incorrect opcodes in trace

[gumb0]

See #5804 (comment)

LegacyVM has optimizations (enabled by default) which need to replace all PUSH6-PUSH32, JUMP, JUMPI opcodes in the original code with synthetic opcodes PUSHC, JUMPC, JUMPCI before the execution.

The problem is that during execution opcode callback gets these synthetic opcodes, this results in VM trace showing them instead of the original ones.

I think this can be fixed by calling the callback in the case of PUSHC, JUMPC, JUMPCI with original opcode instead of m_OP.
The original PUSH can be found from m_code[PUSHC_offset + 3], see

aleth/libevm/LegacyVMOpt.cpp

Line 132 in 9d42e22

m_code[pc+3] = nPush - 2;

The workaround disabling optimizations is cmake .. -DEVM_OPTIMIZE=OFF