Skip to content
Snippets Groups Projects
  1. Jan 03, 2021
    • 8tab's avatar
      Fix global symbols relocations · a7480ea6
      8tab authored
      Instead of a single source of symbols, now linker keeps a list of DSO (former Library) objects
      with their own symbols map. That helps to process R_X86_64_COPY relocations correctly.
      For example, if 'a.out' executable with dependencies ['libstdc++.so', 'libc.so'] is being loaded
      and 'a.out' uses 'stdout' symbol from 'libc.so', its relocation process goes as follows:
      - linker processes relocation entry 'stdout' of type R_X86_64_GLOB_DAT from 'libc.so',
      - it goes through object list ['a.out', 'libstdc++.so', 'libc.so'] to find first object
        that exports 'stdout' symbol. The symbol is in 'a.out' with the value e.g. '0x404070',
      - linker sets 'stdout' symbol GOT entry in 'libc.so' to '0x404070',
      ....
      - linker processes relocation entry 'stdout' of type R_X86_64_COPY from 'a.out',
      - it goes through object list excluding 'a.out': ['libstdc++.so', 'libc.so']. The symbol is found in 'libc.so',
      - linker copies the 'stdout' symbol content from 'libc.so' to memory at address '0x404070' (in 'a.out' object).
      
      Objects are relocated in reverse order they were loaded. So in the example above, linker starts with relocating
      'libc.so' and ends with 'a.out'. It is necessary e.g. when linking with 'libstdc++.so' - there are many
      relocations which symbols are found in 'libstdc++.so', so they need to be resolved before their contents are
      copied to 'a.out'. That also matches GNU ld.so behavior.
      a7480ea6
  2. Dec 24, 2020
  3. Dec 23, 2020
  4. Oct 18, 2020
  5. Oct 06, 2020
  6. Oct 02, 2020
  7. Oct 01, 2020
    • 8tab's avatar
      Fix tls tests for dynamic linker · eee9a80b
      8tab authored
      * load TLS segment for executable - while we can skip PT_LOAD for executable,
        we still have to load TLS segment.
      * set TCB address based on if elf is position independent
      eee9a80b
  8. Sep 30, 2020
  9. Sep 29, 2020
  10. Sep 28, 2020
    • 8tab's avatar
      Add symlink from libc.so to libc.so.6 · c000373a
      8tab authored
      Typically it's the other way around, but we can't have shared library named libc.so.6 in target/release directory.
      cargo includes 'target/release' in LD_LIBRARY_PATH for build script, so even if clean build runs fine,
      every subsquent run will make build script link with relibc.
      c000373a
  11. Sep 17, 2020
  12. Sep 10, 2020
  13. Sep 08, 2020
  14. Sep 06, 2020
Loading