[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Xen-devel] HVM guest debugging
- To: Guy Zana <guy@xxxxxxxxxxxx>, <xen-devel@xxxxxxxxxxxxxxxxxxx>
- From: Keir Fraser <Keir.Fraser@xxxxxxxxxxxx>
- Date: Sun, 11 Nov 2007 15:50:52 +0000
- Delivery-date: Sun, 11 Nov 2007 07:45:44 -0800
- List-id: Xen developer discussion <xen-devel.lists.xensource.com>
- Thread-index: AcgkSmGrcubXbaPbQQCM+8zmWtqsXAAMEFdm
- Thread-topic: [Xen-devel] HVM guest debugging
See XEN_DOMCTL_setdebugging.
-- Keir
On 11/11/07 10:11, "Guy Zana" <guy@xxxxxxxxxxxx> wrote:
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
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel
|
