Tom Rotenberg
2009-Nov-09 19:16 UTC
[Xen-devel] Printing the exact source line in Xen panic call trace
Hi, I am getting a Xen panic, and i would like to know in which line exactly it happens, but the only thing i can see in the Xen panic message are stuff like this: (XEN) Xen call trace: (XEN) [<ffff828c801b6b1c>] emulate_map_dest+0x9c/0x1e0 (XEN) [<ffff828c801b6eb2>] sh_x86_emulate_write__guest_2+0x52/0x1c0 (XEN) [<ffff828c801af4f0>] hvm_emulate_write+0x90/0xa0 (XEN) [<ffff828c801af545>] hvm_read+0x45/0x90 (XEN) [<ffff828c801647e0>] x86_emulate+0x1000/0x11e20 ... Can i make the Xen call trace to print the exact source lines instead of printing function name + offset? Tom _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
Keir Fraser
2009-Nov-09 20:54 UTC
Re: [Xen-devel] Printing the exact source line in Xen panic call trace
On 09/11/2009 19:16, "Tom Rotenberg" <tom.rotenberg@gmail.com> wrote:> Hi, > > Can i make the Xen call trace to print the exact source lines instead > of printing function name + offset?For example, at your shell: # addr2line -e xen/xen-syms 0xffff82c48024c07f /local/scratch/kfraser/xen-unstable.hg/xen/arch/x86/setup.c:434>From that I''m sure you can write a simple script that takes a Xen backtraceand prints it back out, annotated with file and line number information. -- Keir _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
Tom Rotenberg
2009-Nov-09 20:59 UTC
Re: [Xen-devel] Printing the exact source line in Xen panic call trace
Thanks a lot! That''s really helpfull! On Mon, Nov 9, 2009 at 10:54 PM, Keir Fraser <keir.fraser@eu.citrix.com> wrote:> On 09/11/2009 19:16, "Tom Rotenberg" <tom.rotenberg@gmail.com> wrote: > >> Hi, >> >> Can i make the Xen call trace to print the exact source lines instead >> of printing function name + offset? > > For example, at your shell: > # addr2line -e xen/xen-syms 0xffff82c48024c07f > /local/scratch/kfraser/xen-unstable.hg/xen/arch/x86/setup.c:434 > > From that I''m sure you can write a simple script that takes a Xen backtrace > and prints it back out, annotated with file and line number information. > > -- Keir > > >_______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel