WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-devel

[Xen-devel] HVM guest debugging

To: <xen-devel@xxxxxxxxxxxxxxxxxxx>
Subject: [Xen-devel] HVM guest debugging
From: "Guy Zana" <guy@xxxxxxxxxxxx>
Date: Sun, 11 Nov 2007 05:11:19 -0500
Delivery-date: Sun, 11 Nov 2007 02:14:28 -0800
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
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
<Prev in Thread] Current Thread [Next in Thread>