On Fri, May 23, 2008 at 06:37:58PM +0200, vincent-perrier wrote:
> Here is strace (attached file)
This time, it actually sorta worked...
> write(1, "\tvcpu ... ", 10 vcpu ... ) = 10
> msgsnd(4294967295, {4, ptrace: umoven: Input/output error
> 0x4}, 136966304, 0) = -1 ENOSYS (Function not implemented)
> write(1, "OK\n", 3OK
I have no idea why strace thought that was msgsnd - it should have
said SYS_329 or something. The ENOSYS caused by vcpu and ptrace
interacting badly.
It might be that the behavior difference is caused by a context switch
(to strace and back) before vcpu returns to userspace. I saw this
when I was debugging it.
Can you get the full contents of the siginfo that vcpu is returning?
Jeff
--
Work email - jdike at linux dot intel dot com
-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
User-mode-linux-user mailing list
User-mode-linux-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/user-mode-linux-user
