Position-independent code
Jan 13, 2020
38 minute read

In the last article, we found where code was hiding in our samples/hello executable, by disassembling the whole file and then looking for syscalls.

Later on, we learned how to inspect which memory ranges are mapped for a given PID (process identifier). We saw that memory areas weren’t all equal: they can be readable, writable, and/or executable.

Finally, we learned about program headers and how they specified which parts of the executable file should be mapped to which memory areas.

Want to read more?

This post is Patreon-exclusive until January 26, 2020

Become a Patron! 2020-01-26T07:30:00.000Z 2020-01-26T07:30:00.000Z UTC 📖 Position-independent code Now available: https://fasterthanli.me/blog/2020/position-independent-code/ Log in

Become a Patron now to get early access to all my posts. Learn more