• henfredemars@infosec.pub
    link
    fedilink
    English
    arrow-up
    38
    arrow-down
    2
    ·
    edit-2
    10 months ago

    Yes. It’s a surprisingly bad debugger the more you think about it. I use it largely in assembly and it loves to spit out random errors about memory it tried to access based on the current register state. The shortcuts are kind of dumb.

    It certainly works but I wouldn’t call it a pleasure to use.

    Ex: try disp x/1i $eip often just doesn’t work.

    • TunaCowboy@lemmy.world
      link
      fedilink
      arrow-up
      6
      ·
      10 months ago

      I use gdb with great success for x64, rv64, and c:

      info registers rip or just setup tui:

      # ~/.config/gdb/gdbinit:
      tui new-layout default regs 1 {-horizontal src 1 asm 1} 2 status 0 cmd 1
      tui layout default
      tui enable
      
    • xan1242
      link
      fedilink
      arrow-up
      2
      arrow-down
      1
      ·
      10 months ago

      I honestly vastly prefer using IDA and Windows specific tools (x64dbg) over gdb. IDA can interface with gdb so it can act as a frontend which can be handy for visualization.