In-Reply-To: <[email protected]>
On Tue, 17 Jan 2006 at 16:01:52 +0100, Andi Kleen wrote:
> On Tuesday 17 January 2006 16:01, Hugh Dickins wrote:
>
> > I've often found symbolsize useful. Not when looking at an oops
> > from my own machine. But when looking at an oops posted on LKML,
> > from someone who most likely has a different .config and different
> > compiler, different optimization and different inlining from mine.
> > symbolsize is a good clue as to how close their kernel is to the
> > one I've got built on my machine, how likely guesses I make based
> > on mine will apply to theirs, and whereabouts in the function that
> > it oopsed.
>
> Yes that is why I want it too.
OK, how about this: remove the "0x" from the function size, i.e. print:
kernel_symbol+0xd3/10e
instead of:
kernel_symbol+0xd3/0x10e
This saves two characters per symbol and it should still be clear that
the second number is hexadecimal.
Does that break any tools?
--
Chuck
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
[Index of Archives]
[Kernel Newbies]
[Netfilter]
[Bugtraq]
[Photo]
[Stuff]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
[Linux Resources]
