← Back to context Comment by userbinator 5 hours ago Using GDB to debug Asm is... certainly a choice. 5 comments userbinator Reply pjmlp 33 minutes ago Why? Back in the day, after the pain of debugging on Timex, and MS-DOS debug, the confort of Turbo Assembler debugger felt really nice. gopalv 4 hours ago Gdb is an excellent debugger for assembly, even when the original code was written in CI would automatically type(gdb) x/4i $pcwhen 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 5 hours ago What's the better choice? hn_submit 4 hours ago Setting a breakpoint in the debug registers DB0 through DB7 and dumping registers and memory in your own debug exception handler.
pjmlp 33 minutes ago Why? Back in the day, after the pain of debugging on Timex, and MS-DOS debug, the confort of Turbo Assembler debugger felt really nice.
gopalv 4 hours ago Gdb is an excellent debugger for assembly, even when the original code was written in CI would automatically type(gdb) x/4i $pcwhen 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 5 hours ago What's the better choice? hn_submit 4 hours ago Setting a breakpoint in the debug registers DB0 through DB7 and dumping registers and memory in your own debug exception handler.
hn_submit 4 hours ago Setting a breakpoint in the debug registers DB0 through DB7 and dumping registers and memory in your own debug exception handler.
Why? Back in the day, after the pain of debugging on Timex, and MS-DOS debug, the confort of Turbo Assembler debugger felt really nice.
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.
What's the better choice?
Setting a breakpoint in the debug registers DB0 through DB7 and dumping registers and memory in your own debug exception handler.