I see $a, $d and $t symbols in the backtrace/ksymoops output/System.map/linker error messages. What are they and how can I get rid of them ?
These are “mapping symbols”, which are used in the generation of some binary formats, added by binutils 2.15. Unfortunately,they leak into the symbol table, and as such interfere with the linkers ability to find the correct symbol to report for error messages. They also appear in the objdump –syms and nm outputs, and affect the operation of the kernel backtrace and ksymoops outputs. There is no a generally applicable workaround for this issue other than using an earlier binutils version such as 2.14 which may have other issues, as a minimum the 2.14 binutils requires a patch to prevent a silent build error.
[12 July 2004 – rmk] These are “mapping symbols”, which are used in the generation of some binary formats, added by binutils 2.15. Unfortunately, they leak into the symbol table, and as such interfere with the linkers ability to find the correct symbol to report for error messages. They also appear in the objdump –syms and nm outputs, and affect the operation of the kernel backtrace and ksymoops outputs. In order to work around this problem, I recommend not using binutils 2.15 for the time being. Please use an earlier binutils version like 2.14 instead. However, please ensure that you have applied this fix.
Related Questions
- I see $a, $d and $t symbols in the backtrace/ksymoops output/System.map/linker error messages. What are they and how can I get rid of them ?
- I get the following error "Could not create output file (was replacing the original zip file)". What is wrong?
- What is the error: Could not write header for output file (incorrect codec parameters) ?
