Re: [PATCH 0/3] changes about Call Trace:

[Andi Kleen]

On Monday 16 January 2006 14:41, Akinobu Mita wrote:
> On Mon, Jan 16, 2006 at 01:22:11PM +0100, Andi Kleen wrote:
> > 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.
> 
> How about this update?
> 
> 1/3: change from "[<...>]" to  "<...>".
> 2/3: change the format of offset from hexadecimal to decimal in.

Can you please repost it in a fresh thread? I lost track of what was
the latest patch.

In general if you can make the call trace more compact without
losing information it's ok for me. Better wrapping sounds like
a promising approach.

-Andi
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/