From: Andrew Morton <akpm@osdl.org>
To: Chuck Ebbert <76306.1226@compuserve.com>
Cc: linux-kernel@vger.kernel.org, torvalds@osdl.org,
mita@miraclelinux.com, Keith Owens <kaos@ocs.com.au>
Subject: Re: [patch 2.6.15-current] i386: multi-column stack backtraces
Date: Mon, 16 Jan 2006 22:42:34 -0800 [thread overview]
Message-ID: <20060116224234.5a7ca488.akpm@osdl.org> (raw)
In-Reply-To: <200601170126_MC3-1-B602-EFCB@compuserve.com>
Chuck Ebbert <76306.1226@compuserve.com> wrote:
>
> 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.
The patch is a desirable change (I do get seasick reading x86_64 traces,
but I'll get over it), but it'll cause various bits of downstream grief.
next prev parent reply other threads:[~2006-01-17 6:43 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-17 6:23 Chuck Ebbert
2006-01-17 6:39 ` Dave Jones
2006-01-17 6:42 ` Andrew Morton [this message]
2006-01-17 7:58 ` Dave Jones
2006-01-17 8:20 ` Andrew Morton
2006-01-17 10:26 ` Keith Owens
2006-01-17 17:12 ` Jan Engelhardt
2006-01-18 5:23 ` Keith Owens
2006-01-17 10:22 ` Keith Owens
2006-01-17 18:14 ` Sam Ravnborg
2006-01-18 22:47 ` Pavel Machek
2006-01-18 3:05 Chuck Ebbert
2006-01-19 0:36 Chuck Ebbert
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20060116224234.5a7ca488.akpm@osdl.org \
--to=akpm@osdl.org \
--cc=76306.1226@compuserve.com \
--cc=kaos@ocs.com.au \
--cc=linux-kernel@vger.kernel.org \
--cc=mita@miraclelinux.com \
--cc=torvalds@osdl.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®