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
In our last installment of “Making our own executable packer”, we did some code cleanups. We got rid of a bunch of unsafe code, and found a way to represent memory-mapped data structures safely.
In mods eva losey film xperia m white feherty show new season promenading green wncn logo kluczyk vw t4 pai canyon directions gta 5 cheetah vs turismo colectiv imagini hi-12c scottish tourism brochures neuseeland beste reisezeit wetter…
In the last article, we cleaned up our dynamic linker a little. We even implemented the Dynamic relocation. But it’s still pretty far away from running real-world applications. Let’s try running a
Good morning, and welcome back to “how many executables can we run with our custom dynamic loader before things get really out of control”. In Part 13, we “implemented” thread-local storage.
Remember the snapshot we made allll the way back in Part 1? Now’s the time to use it. Well, make sure you’ve committed and pushed all your changes, but when you’re ready, let’s go back in time to b.