Skip to contentSkip to conversation

Oops tracing and /proc

DISCUSSION Lee Revell 2 participants 2 messages Mar 9, 2005

lore
Share & tools
lore

Lee Revell

author
#0 lore raw

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

#1 lore raw
Quoted 9 lines · Lee Revell

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