On 7/8/07 10:29, "Keir Fraser" <keir@xxxxxxxxxxxxx> wrote:
> What would be useful is to try to add tracing to see how far vmxassist gets
> after its last line of tracing before the trap occurs. That last line is
> currently from vm86.c, line 620. You might try adding extra printf()
> statements imemdiately after the write16() on line 622, and also at the top
> of the opcode() function. We need to find out at what point vmxassist is
> jumping to this bogus address d0800.
Oh, another possibility is that vmxassist has been corrupted in memory. This
is particularly likely because, according to the objdump, the 'instruction'
that starts at d0800 is actually valid (it'd be an ADD of some sort).
So, within trap() you might want to read say 16 bytes starting at 0xd0800
and printf() them. So we can see if they match what objdump says should be
there.
 -- Keir
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel