Explore >> Select a destination
|
You are here 
|
blog.k3170makan.com | ||
| | | | |
wiki.osdev.org
|
|
| | | | | [AI summary] The provided text is an in-depth guide to understanding and implementing an ELF (Executable and Linkable Format) loader in low-level programming. It covers key concepts such as ELF headers, section headers, program headers, symbol tables, relocation entries, and the process of loading and executing ELF files. The text also includes code examples for parsing ELF headers, processing relocation entries, and handling memory mapping for segments. | |
| | | | |
www.caichinger.com
|
|
| | | | | Introduction ELF is the file format used for object files (.o's), binaries, shared libraries and core dumps in Linux. It's actually pretty simple and well thought-out. ELF has the same layout for all architectures, however endianness and word size can differ; relocation types, symbol types and the like may have platform-specific values, and of course the contained code is arch specific. An ELF file provides 2 views on the data it contains: A linking view and an execution view. Those two views can be accessed by two headers: the section header table and the program header table. Linking view: Section Header Table (SHT) The SHT gives an overview on the sections contained in the ELF file. Of particular interest are REL sections (relocations), SYMTAB/DYNSYM (sym... | |
| | | | |
binarydodo.wordpress.com
|
|
| | | | | You might want to complement the reading of this article with another related article:Investigating linking with COMMON symbols in ELF I use GCC 4.8.5 in the examples of this article. General classification of symbols Symbols can be classified into different categories, which determines in which section they are found in an ELF file: Defined symbols... | |
| | | | |
ejpcmac.net
|
|
| | | [AI summary] The article provides a comprehensive guide on using Nix for managing development environments, integrating it with tools like direnv for persistent shell configurations, and optimizing the Nix store for disk space. It also discusses the transition from asdf to Nix, highlighting Nix's superior capabilities in environment management and build automation. | ||
