Small update: It seems that double mapping was not the cause. The bug can happen with and without double mapped page tables. Its just sensitive to several things: - putting the int 3 at different locations - excluding a range of pages from being used by the OS loader (marking as firmware) - double mapping page tables
The problem now also happened directly after mapping the PTE. As soon as the behaviour starts it will continue this way, ie when continuing with a fixed rip the next int 3 will also push an rip on the stack that points at the 0xCC It would be really cool if someone could give me a hint what this could be. Thanks, Timo ------------------------------------------------------------------------------ Learn Windows Azure Live! Tuesday, Dec 13, 2011 Microsoft is holding a special Learn Windows Azure training event for developers. It will provide a great way to learn Windows Azure and what it provides. You can attend the event by watching it streamed LIVE online. Learn more at http://p.sf.net/sfu/ms-windowsazure _______________________________________________ VBox-users-community mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/vbox-users-community
