x86 Assembly Questions

$ cat bork.asm

section .data
fuck: dd 0xDEADBEEF

section .text
global _start
_start:
mov dword [fuck],0xABADC0DA

mov eax,1
mov ebx,0
int 0x80


Why doesn't writing to the .data segment segfault? Shouldn't Linux map it to a read-only page?

$ nasm -f elf bork.asm
$ gold -s -o bork-gold bork.asm
$ ld -s -melf_i386 -o bork-ld bork.o
$ du -bh *
432 bork-gold
132 bork.asm
340 bork-ld
608 bork.o


How does such a minimal binary take up 300+ bytes?

>>34
Fuck you, I make a new segment for every function I need and it's never bitten me in the ass.

Who cares about Windows asm any more anyway. Is it because AT&T syntax is such ugly garbage? Yeah, GCC made a blunder choosing that one.

Also, FASM is better than nasm.