From: tj@kernel.org (Tejun Heo)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] stack2core: show stack message and convert it to core file when kernel die
Date: Mon, 04 Jan 2010 08:24:53 +0900 [thread overview]
Message-ID: <4B412745.9070307@kernel.org> (raw)
In-Reply-To: <20100103151406.20228c3a@infradead.org>
On 01/04/2010 08:14 AM, Arjan van de Ven wrote:
>> Whichever one works but s2c wouldn't require symbol decoding. Maybe
>> we can simply add an option to tell it to just parse the oops and
>> output it in machine friendly format. Oh, also, the patch does add
>> new information the module load addresses. We should be able to add
>> those to the oops message in a compact form.
>
> actually one does not need those; you know the start address of the
> function already from the current oops output, and since you know the
> address of the function within the module as well, you know the start
> address of the module.
Right. Thanks for the explanation.
--
tejun
next prev parent reply other threads:[~2010-01-03 23:24 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-03 15:05 [PATCH] stack2core: show stack message and convert it to core file when kernel die Hui Zhu
2010-01-03 16:03 ` Russell King - ARM Linux
2010-01-03 16:30 ` Hui Zhu
2010-01-03 16:44 ` Russell King - ARM Linux
2010-01-03 16:55 ` Hui Zhu
2010-01-03 17:10 ` Russell King - ARM Linux
2010-01-03 17:18 ` Hui Zhu
2010-01-03 17:37 ` Hui Zhu
2010-01-03 17:26 ` Arjan van de Ven
2010-01-03 17:39 ` Hui Zhu
2010-01-03 17:47 ` Russell King - ARM Linux
2010-01-03 18:32 ` Marek Vasut
2010-01-03 22:49 ` Tejun Heo
2010-01-03 23:01 ` Arjan van de Ven
2010-01-03 23:07 ` Tejun Heo
2010-01-03 23:14 ` Arjan van de Ven
2010-01-03 23:24 ` Tejun Heo [this message]
2010-01-04 16:22 ` Hui Zhu
2010-01-04 23:03 ` Tejun Heo
2010-01-05 9:04 ` Hui Zhu
2010-01-05 9:20 ` Tejun Heo
2010-01-06 7:07 ` Hui Zhu
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=4B412745.9070307@kernel.org \
--to=tj@kernel.org \
--cc=linux-arm-kernel@lists.infradead.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;
as well as URLs for NNTP newsgroup(s).