From: Dave Jones <davej@redhat.com>
To: Lee Revell <rlrevell@joe-job.com>
Cc: linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: Oops tracing and /proc
Date: Wed, 9 Mar 2005 00:42:28 -0500 [thread overview]
Message-ID: <20050309054228.GB2531@redhat.com> (raw)
In-Reply-To: <1110346587.7123.14.camel@mindpipe>
On Wed, Mar 09, 2005 at 12:36:27AM -0500, Lee Revell wrote:
> I am trying to decode an Oops per the instructions in
> Documentation/oops-tracing.txt. The instructions say to run it through
> ksymoops with the "-k /proc/ksyms" argument.
>
> But, I do not have this file! The closest thing I have
> is /proc/kallsyms. ksymoops complains that it does not understand the
> syntax of this file.
>
> What am I doing wrong?
If you have CONFIG_KALLSYMS enabled, you don't need ksymoops
as the backtrace gets decoded to symbol names for you.
The only use for ksymoops in a 2.6 kernel is probably the
disassembly of the Code: line.
http://www.kernel.org/pub/linux/utils/kernel/ksymoops/
Dave
prev parent reply other threads:[~2005-03-09 5:42 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-09 5:36 Oops tracing and /proc Lee Revell
2005-03-09 5:42 ` Dave Jones [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20050309054228.GB2531@redhat.com \
--to=davej@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rlrevell@joe-job.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox