|
You are here |
marabos.nl | ||
| | | | |
atilaoncode.blog
|
|
| | | | | I'm fascinated by misconceptions. I used to regularly host pub quizzes (aka trivia nights in some parts of our blue marble), and anyone who's attended a few of my quizzes know that if it sounds like a trick question, it probably is. I've done more than a fair share of "True or False" rounds where... | |
| | | | |
darkcoding.net
|
|
| | | | | Solvitas perambulum | |
| | | | |
morestina.net
|
|
| | | | | In November 2021 I wrote a blog post that examined Rust's curious relationship with global variables. It aimed to explain why this ubiquitous language feature required external crates, and en... | |
| | | | |
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... | ||