Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753483Ab0AEJQV (ORCPT ); Tue, 5 Jan 2010 04:16:21 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1752755Ab0AEJQU (ORCPT ); Tue, 5 Jan 2010 04:16:20 -0500 Received: from hera.kernel.org ([140.211.167.34]:49122 "EHLO hera.kernel.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751722Ab0AEJQR (ORCPT ); Tue, 5 Jan 2010 04:16:17 -0500 Message-ID: <4B430457.5020906@kernel.org> Date: Tue, 05 Jan 2010 18:20:23 +0900 From: Tejun Heo User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.1.5) Gecko/20091130 SUSE/3.0.0-1.1.1 Thunderbird/3.0 MIME-Version: 1.0 To: Hui Zhu 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" , x86@kernel.org, Frederic Weisbecker , Alexey Dobriyan , Brian Gerst , Rusty Russell , Andrew Morton , Steven Rostedt , Greg Kroah-Hartman , "Paul E. McKenney" , linux-arm-kernel@lists.infradead.org, linux-kernel@vger.kernel.org, linux-mips@linux-mips.org, Coly Li Subject: Re: [PATCH] stack2core: show stack message and convert it to core file when kernel die References: <4B411F14.1040302@kernel.org> <20100103150134.5bdab023@infradead.org> <4B412341.2010002@kernel.org> <20100103151406.20228c3a@infradead.org> <4B4273D6.2010306@kernel.org> In-Reply-To: X-Enigmail-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1359 Lines: 36 Hello, 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. markup_oops.pl have itself idea, it try use dmesg| markup_oops.pl > 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. :-) Thanks. -- tejun -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/