Hi,
On 31/10/2007, TeLeMan <[EMAIL PROTECTED]> wrote:
> If the 0x10008000 page is writable and 0x10007FFF isn't, softmmu can raise
> this exception before modifing 0x10007FFF-0x10008002 because softmmu checks
> 0x10007FFF at first. I don't know if reversing the order is an exact
> solution,but its
andrzej zaborowski wrote:
>
> Hi,
>
> On 28/10/2007, TeLeMan <[EMAIL PROTECTED]> wrote:
>> For example, the memory address 0x10008000 is on an unwritable page.When
>> the
>> instruction "add dword ptr [0x10007FFF],0x12345678" is executed,the OS
>> will
>> set 0x10008000 page be a writable page
Hi,
On 28/10/2007, TeLeMan <[EMAIL PROTECTED]> wrote:
> For example, the memory address 0x10008000 is on an unwritable page.When the
> instruction "add dword ptr [0x10007FFF],0x12345678" is executed,the OS will
> set 0x10008000 page be a writable page and re-execute this instruction. But
> softmmu
For example, the memory address 0x10008000 is on an unwritable page.When the
instruction "add dword ptr [0x10007FFF],0x12345678" is executed,the OS will
set 0x10008000 page be a writable page and re-execute this instruction. But
softmmu has modifed the value of 0x10007FFF,so after re-executing thi
