Hi!
> > Print stack backtraces in multiple columns, saving screen space.
> > Number of columns is configurable and defaults to one so
> > behavior is backwards-compatible.
> >
> > Also removes the brackets around addresses when printing more
> > that one entry per line so they print as:
> > <address>
> > instead of:
> > [<address>]
> > This helps multiple entries fit better on one line.
> >
> > Original idea by Dave Jones, taken from x86_64.
> >
>
> Presumably this is going to bust ksymoops. Also the various other custom
> oops-parsers which people have written themselves.
>
> > +config STACK_BACKTRACE_COLS
>
> It's pretty sad to go and make something like this a config option. But
> given that it is, believe it or not, an exported-to-userspace interface, I
> guess there's not much choice.
I don't think we should call printk()s "userspace interface". Yes,
someone may do dmesg | custom-grep-to-find-all-the-hardware, but
thats clearly stupid. I also believe that oops dump is so closely tied
to kernel that it is fair to change... plus this should better not be
configurable, or userspace will have hard time parsing it.
Pavel
--
Thanks, Sharp!
-
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]
