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

[Kip Macy <kip.macy@xxxxxxxxx>]

When one types 'next' in GDB, GDB looks up the address of the first
instruction for the next line of source code and sticks a breakpoint
there. If one 'next's through an inline hypercall function the dom0 has
consistently locked up on me. Next time I think about this problem I'll
enable debug output to find out where the breakpoints are actually
being put.

                     
-Kip

On 12/31/05, Keir Fraser <Keir.Fraser@xxxxxxxxxxxx> wrote:

How do you mean? Replacing hypercall int instruction with int3? I would
expect that to work.

  -- Keir


On 31 Dec 2005, at 04:37, Kip Macy wrote:

> Any thoughts on setting breakpoints around hypercalls?
>
> ---------- Forwarded message ----------
> From: Kip Macy <kip.macy@xxxxxxxxx >
> Date: Dec 26, 2005 12:14 AM
> Subject: setting breakpoints around hypercalls in a domU causes dom0
> to lockup
> To: xen-devel <xen-devel@xxxxxxxxxxxxxxxxxxx >, Keir Fraser
> <Keir.Fraser@xxxxxxxxxxxx >
>
> 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