I've put some xen_raw_printk statements in xen_setup_kernel_pagetable, and I'm 
not seeing the output on the console, even when I use on_crash = 'preserve'. 
So the crash may be happening sooner than that. I've also enabled domU crash 
dumps in xend, but when this crash occurs, the core file is 0 bytes and labeled 
'-incomplete'. Could the crash be happening too early to get a core dump? 
Also, is there anything like ksymoops which I can use to interpret the stack 
trace and find the function where the crash is occurring?
Thanks, 
John A.
-----Original Message-----
From: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx 
[mailto:xen-devel-bounces@xxxxxxxxxxxxxxxxxxx] On Behalf Of Keir Fraser
Sent: Monday, January 04, 2010 2:45 PM
To: Andrew Lyon; Ian Campbell; Xen-devel
Subject: Re: [Xen-devel] PaX Security w/ Kernel.org DomU 2.6.31.7
On 04/01/2010 19:13, "Andrew Lyon" <andrew.lyon@xxxxxxxxx> wrote:
> Daft question, how can I check if the Xen I am running was build with
> debug=y or not?
>>>> (XEN) Unhandled page fault in domain 26 on VCPU 0 (ec=0000)
>>>> (XEN) Pagetable walk from 0000000000000028:
>>>> (XEN)  L4[0x000] = 0000000000000000 ffffffffffffffff
>>>> (XEN) domain_crash_sync called from entry.S
>>>> (XEN) Domain 26 (vcpu#0) crashed on cpu#4:
>>>> (XEN) ----[ Xen-3.1.3  x86_64  debug=y  Not tainted ]----
 ^^^^^^^
 -- Keir
_______________________________________________
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