Messages in this thread | | | Date | Fri, 15 Nov 1996 14:56:22 +0000 (GMT) | From | Bryn Paul Arnold Jones <> | Subject | Re: Oopses not using System.map to translate |
| |
On Fri, 15 Nov 1996, Joseph Wade Breu wrote:
> > Hi all! > > How do I get my kernel to use the System.map file for the kernel > translations? The oops that I reported earlier did not use the file and > therefore I could not translate the buggy command. > > Thanks! >
Ok, there are three ways to translate them:
1. By hand: look up the EIP, and call trace in the System.map and put them in the mail after the oops.
2. With ksymoops: it's a c++ program, it's source is in (the linux source tree in) linux/scripts, read the first few lines to see how to build it. To use it get the oops, and strip off the syslog stuff (if it's got it on), and then do:
ksymoops /path_to_System.map/System.map <oops.txt >decoded.txt
post the oops, and ksymoops output.
3. Automagically: Well klogd will do it for you if it's a farly resent version, it has to be able to find the System.map when it starts (you can tell it to reload them, see klogd(8) ;), and it looks in /boot/System.map, /System.map, and /usr/src/linux/System.map. If it can't find the System.map, make a symbolic link to it in "/" (ie as root 'cd /; ln -s <path to System.map>/System.map').
You can usally find the oops in /var/log/messages (that's where syslog should log it, decoded or otherwise ;)
Bryn -- PGP key pass phrase forgotten, \ Overload -- core meltdown sequence again :( and I don't care ;) | initiated. / This space is intentionally left | blank, apart from this text ;-) \____________________________________
| |