You are not logged in.
Pages: 1
I can't seem to find this file and I need it for analyzing some kernel data. How can I recreate it and why can't I find it in my system?
Last edited by Slavak (2018-05-09 01:37:26)
Offline
Offline
So System.map is basically an alias to kallsyms then?
Offline
Sort of. /proc/kallysms is the definitive table.
Offline
What do you mean by "the definitive table" ?
I still don't get it, before issuing sudo cp /proc/kallsyms /boot/System.map-`uname -r` there was no System.map and AFAIK klogd requires this file in order to properly handle kernel oops so how come I never had any problems without this file and more importantly what's the point of System.map if it's only a copy of kallysms
Offline
What do you mean by "the definitive table" ?
I still don't get it, before issuing sudo cp /proc/kallsyms /boot/System.map-`uname -r` there was no System.map and AFAIK klogd requires this file in order to properly handle kernel oops so how come I never had any problems without this file and more importantly what's the point of System.map if it's only a copy of kallysms
You have never had any problems with what? Or what problems do you expect because of a lack of that file?
Are you replacing the systemd journal with klogd + a syslog of some form?
Edit:
https://cateee.net/lkddb/web-lkddb/KALLSYMS.html
https://www.kernel.org/doc/html/latest/ … nting.html
Last edited by loqs (2018-05-06 22:57:15)
Offline
I was expecting a crash really, but I just read the article you linked and now I see why...
The question now is: why doesn't arch create the system.map file by default?
Last edited by Slavak (2018-05-07 01:15:02)
Offline
Just found out that kallsyms have symbols of dynamically loaded modules and static code whereas system.map contains symbols for static code only, which renders system.map pretty much useless, still don't get the point for its existence.
Last edited by Slavak (2018-05-07 01:29:53)
Offline
Pages: 1