Ok, so I understand that we have all our C / C ++ programmers at one time, our unusual slavery, demonic signs, SIGSEGV, Segmentation fault now, I (emphasis on the last stress) This magical GCC (or G ++) The compiler, or what you have, is understood to have some form of unsuccessful safe / checking system within certain parts of the machine code. But! Today I was walking with some old X86 codear with a good old NASM on virtualized arch Linux system, and for a lot of my surprise and contemplation, once again failed by my coding efforts by Naphitius Segfault. The code that generates a dangerous signal: mov eax, 0x7 mov [0xB8000], eax Now, I Understand that the Linux kernel loads your assembled program in a shell and executes it from there, but I thought it talks with the MOV instructions processor in 1 to 1, how the Earth can detect the kernel I'm trying to use a little memory, it does not want me, and the instructions Central? I do not pretend to understand that when your...