Explore >> Select a destination
|
You are here 
|
lwn.net | ||
| | | | |
jmmv.dev
|
|
| | | | | In a recent work discussion, I came across an argument that didn't sound quite right. The claim was that we needed to set up containers in our developer machines in order to run tests against a modern glibc. The justifications were that using LD_LIBRARY_PATH to load a different glibc didn't work and statically linking glibc wasn't possible either. But... running a program against a version of glibc that's different from the one installed on the system seems like a pretty standard requirement, doesn't it?... | |
| | | | |
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. | |
| | | | |
shrik3.com
|
|
| | | | | [AI summary] The user provided a detailed explanation of dynamic linking in the context of ELF binaries, covering topics such as the ELF format, symbol resolution, the dynamic linker, and various tools and functions involved in the process. They also mentioned other resources for further reading and included some additional content about the a.out format and other programming concepts. The user's message seems to be a comprehensive overview of dynamic linking and related topics, possibly for educational or reference purposes. | |
| | | | |
blog.nuculabs.dev
|
|
| | | I've recently finished reading a book called Practical Binary Analysis which I consider a state of the art book (review will come soon) and I would like to post my solution to the crackme found in chapter 5. | ||
