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

Re: [Xen-devel] double fault ...


You compile with crash_debug=y?

Yes.  Mostly to get a xen binary without optimization and with full
debug info, so I can easily lookup stuff using
        "objdump -dS xen-syms | less +/<addr>".

Probably 'debug=y' should also cause -g compilation. I'll add that in.

I presume you do 'optimize=n' to turn off things like -O3?

The intention is that do_int3() will execute DEBUGGER_trap_fatal()
before panic(), so you should enter the gdb stub rather than
infinitely loop. How is that not occurring?

I don't actually have a debugger attached, so DEBUGGER_trap_fatal
aka __trap_to_cdb() instantly returns.

I see. I'll check in a fix.

Thanks!

 -- Keir


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

<Prev in Thread] Current Thread [Next in Thread>