I used to be excited about printing data layouts the way DDD or Rizin do it, but lately I've been getting into GDB pretty printers. They aren't very difficult to write (once you grasp the basics of the GDB API and compiler debug info flags), and they're a very cheap way to make reasonably pleasant representations of data structures. Although "cheap" is not "free", like these sort of tools are.
I don't use GDB a lot. But when I do, I generally use the pwndb extension.
It's written for exploit development, but even for debugging a C program. It makes things a lot nicer.
I love pwndbg. I work at the level of writing syscalls often, and it's wonderful that pwndbg's disassembler pretty-prints the operands of syscalls write next to the actual instruction.
I used to be excited about printing data layouts the way DDD or Rizin do it, but lately I've been getting into GDB pretty printers. They aren't very difficult to write (once you grasp the basics of the GDB API and compiler debug info flags), and they're a very cheap way to make reasonably pleasant representations of data structures. Although "cheap" is not "free", like these sort of tools are.
I don't use GDB a lot. But when I do, I generally use the pwndb extension. It's written for exploit development, but even for debugging a C program. It makes things a lot nicer.
https://pwndbg.re/
I love pwndbg. I work at the level of writing syscalls often, and it's wonderful that pwndbg's disassembler pretty-prints the operands of syscalls write next to the actual instruction.