From: Keith Owens <kaos@ocs.com.au>
To: Andrew Morton <akpm@osdl.org>
Cc: Chuck Ebbert <76306.1226@compuserve.com>,
linux-kernel@vger.kernel.org, torvalds@osdl.org,
mita@miraclelinux.com
Subject: Re: [patch 2.6.15-current] i386: multi-column stack backtraces
Date: Tue, 17 Jan 2006 21:22:09 +1100 [thread overview]
Message-ID: <9554.1137493329@ocs3.ocs.com.au> (raw)
In-Reply-To: Your message of "Mon, 16 Jan 2006 22:42:34 -0800." <20060116224234.5a7ca488.akpm@osdl.org>
Andrew Morton (on Mon, 16 Jan 2006 22:42:34 -0800) wrote:
>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.
Should not be a problem for ksymoops. Most entries use this regex,
where [ ] is optional.
#define BRACKETED_ADDRESS "\\[*<([0-9a-fA-F]{4,})>\\]* *"
Printing multiple addresses (with our without [ ]) plus their symbols
on the same line will stop ksymoops processing at the first symbol
name, but who cares? If you can print a symbol then you already have
kallsyms and you do not need ksymoops. If you do not have kallsyms
then the output is just multiple addresses on one line, which ksymoops
already handles.
next prev parent reply other threads:[~2006-01-17 10:22 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-17 6:23 [patch 2.6.15-current] i386: multi-column stack backtraces Chuck Ebbert
2006-01-17 6:39 ` Dave Jones
2006-01-17 6:42 ` Andrew Morton
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 [this message]
2006-01-17 18:14 ` Sam Ravnborg
2006-01-18 22:47 ` Pavel Machek
-- strict thread matches above, loose matches on Subject: below --
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=9554.1137493329@ocs3.ocs.com.au \
--to=kaos@ocs.com.au \
--cc=76306.1226@compuserve.com \
--cc=akpm@osdl.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.