[Top] [All Lists]

Re: [PATCH] stack2core: show stack message and convert it to core

To: Hui Zhu <>
Subject: Re: [PATCH] stack2core: show stack message and convert it to core file when kernel die
From: Tejun Heo <>
Date: Tue, 05 Jan 2010 18:20:23 +0900
Cc: Arjan van de Ven <>, Russell King <>, saeed bishara <>, Catalin Marinas <>, Nicolas Pitre <>, Ralf Baechle <>, David Daney <>, Tomaso Paoletti <>, Chris Dearman <>, Paul Gortmaker <>, Thomas Gleixner <>, Ingo Molnar <>, "H. Peter Anvin" <>,, Frederic Weisbecker <>, Alexey Dobriyan <>, Brian Gerst <>, Rusty Russell <>, Andrew Morton <>, Steven Rostedt <>, Greg Kroah-Hartman <>, "Paul E. McKenney" <>,,,, Coly Li <>
In-reply-to: <>
References: <> <> <> <> <> <> <> <>
User-agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv: Gecko/20091130 SUSE/3.0.0-1.1.1 Thunderbird/3.0

On 01/05/2010 06:04 PM, Hui Zhu wrote:
> I agree with read the current stack message is better.
> About the extending, I have some question with it:
> 1. have itself idea, it try use dmesg|
> show what happen to usr.  This is different with s2c.
> I am not sure people like it have other function with it.  Too much
> part of this file need to be change.  It need rewrite, just the oops
> message parse part can be keep.

Yeah, I think you'll need to refactor it and share only the parsing
frontend.  Just adding a switch (-m or whatever) which puts it into
machine-friendly translator mode should do the trick.

> 2.  I use perl to work in a long time before, I know it good at parse
> the text, but I am not sure it good at handle struct like:

You don't need to handle the data structure at all.  Just make it
parse the dmesg and output machine-friendly formatted output which can
be processed by s2c.  ie. just make it do the reformatting.

> Even if what happen, I will keep a c s2c with myself.  :)

That will be sad.  I really want it too.  :-)



<Prev in Thread] Current Thread [Next in Thread>