• Hazzia@discuss.tchncs.de
          link
          fedilink
          arrow-up
          4
          ·
          11 months ago

          I also work with 20 year old spaghetti code, but my software is primarily middleware and debuggers aren’t allowed on the full system where I’d actually be able to reproduce the issue. Insane amounts of logging statements have become my most treasured tool.

      • erogenouswarzone@lemmy.ml
        link
        fedilink
        English
        arrow-up
        3
        arrow-down
        1
        ·
        1 year ago

        Yes, but only because it gives you a link to where that was run. Click the link to the right with filename:lineNumber, and it will open the sources tab to that line. Set a breakpoint and rerun to pause there, then step through the code’s execution.

        Of course, if you’re using minified or processed code, this will be more difficult, in that case figure out how to do it in VS Code.

      • erogenouswarzone@lemmy.ml
        link
        fedilink
        arrow-up
        5
        ·
        1 year ago

        Yep. Once you get the hang of it, you will cringe to think of all the wasted effort that came before. But getting the hang of it takes dedication.

        • AlexWIWA@lemmy.ml
          link
          fedilink
          arrow-up
          1
          ·
          1 year ago

          Thankfully I use python mostly and pycharm makes it easy-ish to get the debugger hooked up to a project. But learning that process definitely took a few days

    • CanadaPlus@lemmy.sdf.org
      link
      fedilink
      arrow-up
      3
      ·
      1 year ago

      Does this include C programmers? I’ve definitely found GDB to be indispensable in the past (or maybe that’s what they would want you to think).

    • theherk@lemmy.world
      link
      fedilink
      arrow-up
      3
      arrow-down
      1
      ·
      1 year ago

      After decades of print debugging I finally got dap up and running in vim. It is very nice. Would recommend.