[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Xen-devel] setting breakpoints around hypercalls in a domU causes dom0 to lockup

To: xen-devel <xen-devel@xxxxxxxxxxxxxxxxxxx>, Keir Fraser <Keir.Fraser@xxxxxxxxxxxx>
From: Kip Macy <kip.macy@xxxxxxxxx>
Date: Mon, 26 Dec 2005 00:14:35 -0600
Delivery-date: Mon, 26 Dec 2005 06:18:16 +0000
Domainkey-signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:reply-to:to:subject:mime-version:content-type; b=YB3TZ9CuVBBwF6CTQfPjh59E58QasJp1pmYKaBPgeLXchNijs2OOZJg1sfQNpsTxE2zyFdhnCH8/FVapt+8oCnkNde0rSYoPJoPJpoh/0mgGbmQhkHa1XiaXHYz2/cLqoGPvuqDpor8AGngak/OIYnPAArrnap08ig3yBHBxPbA=
List-id: Xen developer discussion <xen-devel.lists.xensource.com>

Stepping through hypercalls (at the source level, not using the trace trap) causes my dom0 to lockup. Might xen be receiving the int3 and not realize whom to forward to?

-Kip

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel

Prev by Date: [Xen-devel] [PATCH] Fixing an unnatural error message of vcpu-list in main.py
Next by Date: [Xen-devel] How to redirect domU port to dom0 with nat
Previous by thread: [Xen-devel] [PATCH] Fixing an unnatural error message of vcpu-list in main.py
Next by thread: [Xen-devel] How to redirect domU port to dom0 with nat
Index(es):
- Date
- Thread

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.