Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id ; Thu, 31 Oct 2002 16:01:36 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id ; Thu, 31 Oct 2002 16:01:36 -0500 Received: from to-velocet.redhat.com ([216.138.202.10]:3833 "EHLO touchme.toronto.redhat.com") by vger.kernel.org with ESMTP id ; Thu, 31 Oct 2002 16:01:34 -0500 Date: Thu, 31 Oct 2002 16:08:00 -0500 From: Benjamin LaHaise To: Linus Torvalds Cc: Andreas Herrmann , linux-kernel@vger.kernel.org, lkcd-devel@lists.sourceforge.net, lkcd-devel-admin@lists.sourceforge.net, lkcd-general@lists.sourceforge.net, Rusty Russell , "Matt D. Robinson" Subject: Re: [lkcd-devel] Re: What's left over. Message-ID: <20021031160800.M18072@redhat.com> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5.1i In-Reply-To: ; from torvalds@transmeta.com on Thu, Oct 31, 2002 at 12:40:28PM -0800 Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 978 Lines: 23 On Thu, Oct 31, 2002 at 12:40:28PM -0800, Linus Torvalds wrote: > 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. > > Read my emails. That is one of the reasons that crash dumps are useful. Quite a few problems that customers hit are not easy to reproduce, but when they provide a dump file that can be loaded into gdb with the original kernel debugging info and the backtrace command issued and various bits of internal structures examined, usually a good hypothesis can be made for the cause. Feed that back into a code audit and you end up fixing problems that are decidedly challenging. -ben -- "Do you seek knowledge in time travel?" - 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/