The thing a programmer probably does most is, unsurprisingly, debugging. Not that programmers necessarily love debugging, but if you don't have a high pain tolerance for debugging, you probably don't want to pursue a career in programming. On the other hand, if you like the challenge of the bug hunt, you should try getting into this biz. Or into exterminating. Whatever makes you happy, man.
Anyway, my recent posting on Intel Assembly Language Programming on Mac OS X kinda left you hanging in the air on this one. I didn't say anything about debugging. Why? Because, honestly, I hadn't got that far yet. Of course, the first bug didn't leave me waiting for long, so here's some handy tools if you want to debug your assembler program.
First, you need to compile your assembler source files with GCC using the -g option. That will give you debug symbols, which means the debugger will show you each line. Once you've done that, you just launch GDB, on the command line, as usual:
% gdb path/to/your/executable
You'll get the GDB prompt you may have already seen in Xcode's debugger console. Type in
and it will jump to the start of your main function. GDB will always print the next line, and you can use the step command to execute it and see the next one. Of course, you may want to see what is in a particular register or at a particular memory address. Easy:
(gdb) print/x $eax
will print register eax as hexadecimal (that's what the '/x' means - there's also '/d' for decimal, '/c' for character, '/s' for string and '/t' for binary). If you want to view a memory location, you use the 'x' command instead.
(gdb) x/1xb $eax
will take the address in $eax, and print 1 byte at that address in hexadecimal. The parts after the slash decode into /<count><displayFormat><type>. displayFormat is the same as the thing after the slash when you print, count is a number indicating how many to print, and type is 'b' for byte, 'h' for halfword (2 bytes) or 'w' for word (4 bytes).
Oh yeah and to get out of gdb again, the command is quit. Happy debugging!
Update: I recently realized I'd omitted two important little tricks from this description: If you don't have debug symbols, you can still step through code. The relevant commands are
which steps through code by one instruction (this even works with system functions etc.) and
which disassembles and prints the current instruction.