klogd usage for debugging oops
From: AP (aijaz.pathan_at_voxpath.com)
Date: 17 Dec 2003 16:28:52 -0800
I am trying to use klogd for the first time to identify function name
+ modules name when an "oops" segmentation error occurs.
I went through the klogd man pages and did the following -
- exported my experimental function name (in my externally loaded
module) in which I'm deliberately causing a NULL reference. (Is there
a way around this?)
- started my linux box (XSCALE arch.)
- started the klogd ( I tried all sorts of options -c 7, -p, -s, etc.)
- did a klogd -I so that it gets the kernel symbols from System.map.
- unloaded an old module from the kernel doing an rmmod.
- did a klogd -i to refresh klogd as suggested in man pages.
- loaded my new test module with the pointer violation.
- Did a klogd -i
- Now I caused the memory violation by an external action. The dump
that I get on the console gives me all the Hex values, and the console
hex value of the PC (Program Counter) matches with the hex address at
which the crash causing function is located (in the ksyms file), but
somehow this address is not translated to the symbol name on the
screen dump. Am I missing any config step? Or is there another reason?
Thanks in advance.