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

[Xen-devel] HVM guest debugging


  • To: <xen-devel@xxxxxxxxxxxxxxxxxxx>
  • From: "Guy Zana" <guy@xxxxxxxxxxxx>
  • Date: Sun, 11 Nov 2007 05:11:19 -0500
  • Delivery-date: Sun, 11 Nov 2007 02:14:28 -0800
  • List-id: Xen developer discussion <xen-devel.lists.xensource.com>
  • Thread-index: AcgkSmGrcubXbaPbQQCM+8zmWtqsXA==
  • Thread-topic: HVM guest debugging

In vmx.c, in the vmexit handler (reason = EXIT_REASON_EXCEPTION_NMI)
I found this code:
 
        switch ( vector )
        {
        case TRAP_debug:
        case TRAP_int3:
            if ( !v->domain->debugger_attached )
                goto exit_and_crash;
            domain_pause_for_debugger();
 
Now, I don't understand who updates debugger_attached for a HVM guest.
(I worked with windbg in order to debug a windows HVM, and I guess EXIT_REASON_EXCEPTION_NMI is the exit reason for breakpoints I placed)
 
Can anyone clear this for me?
 
Thanks,
Guy.
 
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel

 


Rackspace

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