Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id ; Thu, 31 Oct 2002 15:46:04 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id ; Thu, 31 Oct 2002 15:46:04 -0500 Received: from excalibur.cc.purdue.edu ([128.210.189.22]:49426 "EHLO ibm-ps850.purdueriots.com") by vger.kernel.org with ESMTP id ; Thu, 31 Oct 2002 15:46:03 -0500 Date: Thu, 31 Oct 2002 15:54:02 -0500 (EST) From: Patrick Finnegan To: Linus Torvalds cc: Andreas Herrmann , , , , , Rusty Russell , "Matt D. Robinson" Subject: Re: [lkcd-devel] Re: What's left over. In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1096 Lines: 33 On Thu, 31 Oct 2002, Linus Torvalds wrote: > On Thu, 31 Oct 2002, Andreas Herrmann wrote: > > > > A dump mechanism within the kernel is a base for much easier > > kernel debugging. > > IMHO, analyzing a dump is much more effective than guessing > > a kernel bug solely with help of an oops message. > > And imnsho, debugging the kernel on a source level is the way to do it. > > Which is why it's not going to be me who merges it. But, LKCD is useful also for tracing crashes back to hardware that causes it. It's really hard to find problems in hardware using source code, since the source code DOENS'T have anything to do with the problems. Pat -- Purdue Universtiy ITAP/RCS Information Technology at Purdue Research Computing and Storage http://www-rcd.cc.purdue.edu http://dilbert.com/comics/dilbert/archive/images/dilbert2040637020924.gif - 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/