System.map
In-game article clicks load inline without leaving the challenge.
In Linux, the System.map file is a symbol table used by the kernel.
A symbol table is a look-up between symbol names and their addresses in memory. A symbol name may be the name of a variable or the name of a function. The System.map is required when the address of a symbol name, or the symbol name of an address, is needed. It is especially useful for debugging kernel panics and kernel oopses. The kernel does the address-to-name translation itself when CONFIG_KALLSYMS is enabled so that tools like ksymoops are not required.
Internals
The following is part of a System.map file:
Because addresses may change from one build to the next, a new System.map is generated for each build of the kernel.
Symbol types
The character between the address and the symbol (separated by spaces) is the type of a symbol. The nm utility program on Unix systems lists the symbols from object files. The System.map is directly related to it, in that this file is produced by nm on the whole kernel program – just like nm lists the symbols and their types for any small object programs.
Some of these types are:
Afor absoluteBorbfor uninitialized data section (called BSS)Dordfor initialized data sectionGorgfor initialized data section for small objects (global)ifor sections specific to DLLsNfor debugging symbolpfor stack unwind sectionRorrfor read only data sectionSorsfor uninitialized data section for small objectsTortfor text (code) sectionUfor undefinedVorvfor weak objectWorwfor weak objects which have not been tagged so-for stabs symbol in an a.out object file?for "symbol type unknown"
Filesystem location
After building the Linux kernel, System.map is located in the root of the source directory. However, some further software installation steps expect to locate the file elsewhere:
- as
/boot/System.map-$(uname -r) - building SVGAlib expects to find
/lib/modules/$(uname -r)/build/System.map