On Fri, Feb 19, 2016 at 12:53 AM, Egbert S. wrote:
> I have here a case (over at GitHub unicorn-engine/unicorn
> tests/unit/test_tb_x86.c) that is running a stack-based Alpha-Mixed sample
> that contains an instruction that changed an operand of the next
> instruction, the one that QEMU does not d
Your solution seems sane, but I'd like a better understanding of what
happens. Therefore...
On 18/02/2016 17:53, Egbert S. wrote:
> As a result, the newly reconstructed TB rebuilds the 'imul'
> micro-operation sequence , but still retrieving the original 0x51
> immediate byte operand (and not the
I have here a case (over at GitHub unicorn-engine/unicorn
tests/unit/test_tb_x86.c) that is running a stack-based Alpha-Mixed sample that
contains an instruction that changed an operand of the next instruction, the
one that QEMU does not detect nor execute properly (even with
TARGET_HAS_PRECISE
