* Oops tracing and /proc
@ 2005-03-09 5:36 Lee Revell
2005-03-09 5:42 ` Dave Jones
0 siblings, 1 reply; 2+ messages in thread
From: Lee Revell @ 2005-03-09 5:36 UTC (permalink / raw)
To: linux-kernel
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?
Lee
^ permalink raw reply [flat|nested] 2+ messages in thread
* Re: Oops tracing and /proc
2005-03-09 5:36 Oops tracing and /proc Lee Revell
@ 2005-03-09 5:42 ` Dave Jones
0 siblings, 0 replies; 2+ messages in thread
From: Dave Jones @ 2005-03-09 5:42 UTC (permalink / raw)
To: Lee Revell; +Cc: linux-kernel
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
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2005-03-09 5:42 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2005-03-09 5:36 Oops tracing and /proc Lee Revell
2005-03-09 5:42 ` Dave Jones
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox