From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S262229AbUCADXq (ORCPT ); Sun, 29 Feb 2004 22:23:46 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S262232AbUCADXq (ORCPT ); Sun, 29 Feb 2004 22:23:46 -0500 Received: from mtvcafw.sgi.com ([192.48.171.6]:42011 "EHLO rj.sgi.com") by vger.kernel.org with ESMTP id S262229AbUCADXp (ORCPT ); Sun, 29 Feb 2004 22:23:45 -0500 X-Mailer: exmh version 2.5 01/15/2001 with nmh-1.0.4 From: Keith Owens To: Zwane Mwaikambo Cc: Linux Kernel , Andrew Morton Subject: Re: [PATCH][2.6] linux/README update In-reply-to: Your message of "Fri, 27 Feb 2004 08:18:20 CDT." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 01 Mar 2004 14:23:01 +1100 Message-ID: <3596.1078111381@kao2.melbourne.sgi.com> Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org On Fri, 27 Feb 2004 08:18:20 -0500 (EST), Zwane Mwaikambo wrote: >- - You can use the "ksymoops" program to make sense of the dump. This >- utility can be downloaded from >+ - If you compiled the kernel with CONFIG_KALLSYMS you can send the dump >+ as is, otherwise you will have to use the "ksymoops" program to make >+ sense of the dump. This utility can be downloaded from ksymoops is still useful even when CONFIG_KALLSYMS is on. ksymoops decodes the Code: line, kallsyms does not. Also kallsyms only handles code addresses[*], ksymoops handles all symbols. [*] Rusty's definition of "all symbols" does not not match mine. kallsyms in 2.6 should really be "ksomesyms".