[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Xen-devel] Printing the exact source line in Xen panic call trace


  • To: Keir Fraser <keir.fraser@xxxxxxxxxxxxx>
  • From: Tom Rotenberg <tom.rotenberg@xxxxxxxxx>
  • Date: Mon, 9 Nov 2009 22:59:49 +0200
  • Cc: "xen-devel@xxxxxxxxxxxxxxxxxxx" <xen-devel@xxxxxxxxxxxxxxxxxxx>
  • Delivery-date: Mon, 09 Nov 2009 13:00:33 -0800
  • Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; b=b4kahcH7yDmFJVZrou8/izZ98SEVYZ3oRCPnOz5IoFrgVgvTk/xOY79KCtrOpQIp9z zSgzGPL7wpIXs2cvBJPMBkBzMZ/0mQ1cm++aiCgPG5jBh3h+gzx/YJ5ZWgLZHIwNkuzn s8FeZychsLtewskyTLsYGYb0yRRpMaQlri+9g=
  • List-id: Xen developer discussion <xen-devel.lists.xensource.com>

Thanks a lot!
That's really helpfull!

On Mon, Nov 9, 2009 at 10:54 PM, Keir Fraser <keir.fraser@xxxxxxxxxxxxx> wrote:
> On 09/11/2009 19:16, "Tom Rotenberg" <tom.rotenberg@xxxxxxxxx> 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@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel


 


Rackspace

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.