Don't forget to call FlushInstructionCache once you're done writing to memory before you jump to it. ARM CPUs are not x86's - they don't maintain coherence between the data and instruction caches like x86 processors do.
---------- Post added 15th November 2013 at 12:03 AM ---------- Previous post was 14th November 2013 at 11:54 PM ----------
Originally Posted by sireangelus
..does it mean that we could have some sort of webkit/blink on the phone, if only devs would be so polite to spend some time on it?
The exception and interrupt handlers of the Windows RT and Windows Phone kernels always set the Thumb bit of the CPSR register in the frozen thread's context. This means that if the interrupted thread was running ARM code, when it resumes, it will crash.
Chrome's V8 generates ARM code, not Thumb-2, as does Firefox's code generator. This is a massive reason why these browsers haven't been ported to Windows RT, let alone Windows Phone.
This can be fixed with kernel patches, but this would require jailbreaking Windows RT or Windows Phone, and defeating PatchGuard.