Messages in this thread |  | | | From | Andi Kleen <> | | Subject | Re: [PATCH 0/3] changes about Call Trace: | | Date | Mon, 16 Jan 2006 13:22:11 +0100 |
| |
On Monday 16 January 2006 13:16, Akinobu Mita wrote: > If I'm missing something, please let me know. > > a) On x86-64 we get different Call Trace format than other architectures > when we get oops or press SysRq-t: > > <ffffffffa008ef6c>{:jbd:kjournald+1030} > > There is a architecture independent function print_symbol(). > How about using it on x86-64? But it changes to: > > [<ffffffffa008ef6c>] kjournald+0x406/0x578 [jbd]
The x86-64 format is more compact.
> b) I can't find useful usage for the symbol size in print_symbol(). > And symbolsize seems to be fixed when vmlinux or modules are compiled. > So we can calculate it from vmlinux or modules. > How about removing the field of symbolsize in print_symbol()? > > [<ffffffffa008ef6c>] kjournald+0x406 [jbd]
It's a double check that the oops is matching the vmlinux you're looking at.
-Andi
- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
|  |