Assembly Nights

Here’s an archive.org mirror of the broken “Why no one should use the AT&T syntax ever, for any reason, under any circumstances” link: https://web.archive.org/web/20251128060318/https://outerprod...

hn_submit an hour ago | parent | prev | next [-]

Why would one choose NASM over FASM? The makers of KolibriOS (an OS written entirely in assembler) chose FASM but the reason eludes me.

To me all assemblers look alike and it would even be feasible to write one's own just for the heck of it.

cellsstudio 42 minutes ago | parent | prev | next [-]

Anyone noticing some pretty heavy skill atrophy from all the Claude/Codex use in the last few months?

I feel like this is a great way to get back to basics and keep the eng skills sharp. Maybe I should try something similar...

	▲	userbinator 39 minutes ago \| parent [-]
		I wouldn't call it "atrophy" unless you were already reading and writing Asm regularly.

Using GDB to debug Asm is... certainly a choice.

gopalv 2 minutes ago | parent | next [-]

Gdb is an excellent debugger for assembly, even when the original code was written in C

I would automatically type

(gdb) x/4i $pc

when opening a coredump out of habit.

But using nasm, then looking as gas style assembly in the debugger might be a bit more jarring.

nekiwo an hour ago | parent | prev | next [-]

What's the better choice?

	▲	hn_submit 3 minutes ago \| parent [-]
		Setting a breakpoint in the debug registers DB0 through DB7 and dumping registers and memory in your own debug exception handler.

an hour ago | parent | prev [-]

[deleted]