e(env, _pc, _cs_base,
> _flags);
>}
> #endif /* TARGET_HAS_PRECISE_SMC */
> It just so happens I am experiencing such a case.
On 14 January 2016 at 11:58, Peter Maydell <peter.mayd...@linaro.org> wrote:
> On 14 January 2016 at
Again, sorry for the personal message, Peter, Google really is failing
here, more so than me.
>> But in my case, an instruction did forward modify some code, but this if
statement did not execute and QEMU executed the old code.
On 14 January 2016 at 16:28, farmdve <farm...@gmail.c
x
inc ebx
inc ebx
inc ebx
inc ebx
inc ebx
inc ebx
aaa
push ecx
pop edx
push 41
pop eax
push eax
xor byte ptr ds:[ecx+30],al
inc ecx
imul eax,dword ptr ds:[ecx+41],51 <-- should multiply with 0x10, not 0x51.
The code is position independent.
On 14 January 2016 at 16:36, Peter Maydell <pe
On Windows, in software MMU mode, how does QEMU handle self-modifying code?
Thank you.
I've been looking and looking, but it must be defined via a macro, I wish
to see it's members.
The rep stosd instruction seems to be jitted in a really weird way and I
was wondering what are the design choices behind this.
Basically the code is jitted to an operation where there is a conditional
branch that tests the ECX register to see if it's zero or not(although I
could have gotten this
