Explore >> Select a destination
|
You are here 
|
krinkinmu.github.io | ||
| | | | |
cpu.land
|
|
| | | | | Curious exactly what happens when you run a program on your computer? Learn how multiprocessing works, what system calls really are, how computers manage memory with hardware interrupts, and how Linux loads executables. | |
| | | | |
patshaughnessy.net
|
|
| | | | | [AI summary] The article discusses the process of learning to read x86 assembly language, focusing on how it can be a useful skill for understanding low-level operations of microprocessors. It outlines the challenges of reading assembly, especially in debugging scenarios, and provides an example of translating Ruby code into x86 assembly using Crystal. The article also explains the syntax and structure of x86 assembly, including register usage, instruction suffixes, and the differences between AT&T and Intel syntax. It highlights the complexity of x86 assembly due to its historical evolution and the need for understanding register sizes and operand notation. | |
| | | | |
book.hacktricks.xyz
|
|
| | | | | ||
| | | | |
austinmorlan.com
|
|
| | | I recently purchased a new laptop (Dell XPS 13 9370) and needed to install Arch onto it. I thought I'd finally document the steps I took because I always seem to forget what I did the last time (one of the joys of Arch is that it rarely needs to be reinstalled). There are a lot of helpful guides online about different installation setups, but I could never find one that met all of my requirements: | ||
