I've never learned how to use a debugger. It's just a lot of console outputs

I've never learned how to use a debugger
It's just a lot of console outputs

  1. 1 week ago
    Anonymous

    You've never worked on a big codebase. You haven't missed anything except hours of frustration

  2. 1 week ago
    Anonymous

    When i learned using debugger, it made things so much easier it felt like cheating.
    I seriously recommend learning how to use it.

    • 1 week ago
      sega

      how did he do that?

  3. 1 week ago
    Anonymous

    is this a meme? are people really this retarded?
    you just put the "red dot" on the left side of your code and hit f5. thats it now you can step through your code and change values and shit. you dont have to know super advanced debugging features to gain huge value from it

    • 1 week ago
      Anonymous

      How can I get this red dot?
      I code in notepad++

      • 1 week ago
        Anonymous

        draw it on your screen with a dry erase marker

      • 1 week ago
        Anonymous

        I did this, nothing happened. Using neovim btw. Any help? Thanks.

        if you are a tinkertranny feel free either install vscode with the codelldb plugin (pic related) or use gdb and the command line like the tranny you are

        • 1 week ago
          Anonymous

          wrong pic (kinda)

        • 1 week ago
          Anonymous

          Yeah ngl kinda tired of tinker trannying. If there was a text editor that was as fast as nvim and had as good of a GUI layer as vscode I would switch immediately. I think jetbrains is working on a vscode competitior, might be worth th switch if they don't fuck it up, called Fleet IIRC.

        • 1 week ago
          Anonymous

          Yeah ngl kinda tired of tinker trannying. If there was a text editor that was as fast as nvim and had as good of a GUI layer as vscode I would switch immediately. I think jetbrains is working on a vscode competitior, might be worth th switch if they don't fuck it up, called Fleet IIRC.

          there is nothing wrong with wanting to understand your tools instead of pressing the magic button

          • 1 week ago
            Anonymous

            Sure I just wished those tools were standardized better (nvim getting there with the LSP support). In the meanwhile, the time investment required to get shit working again when ever you change languages/tools/environment/etc. continues to bother me.
            If a company comes along and offers:
            >Literally just works fast, light weight editor
            >Standardized ways to extend functionality (eg. LSP and an established scripting language)
            I would switch because why not. So far, no such luck

            • 1 week ago
              Anonymous

              how much is involved for you to get going in different languages? isnt it just plug new LSP and play?

      • 1 week ago
        Anonymous

        kill yourself you worthless retard

    • 1 week ago
      Anonymous

      I did this, nothing happened. Using neovim btw. Any help? Thanks.

  4. 1 week ago
    Anonymous

    for me its gdb

  5. 1 week ago
    Anonymous

    No need, I rarely use the debugger, only if I've sat hours with a problem and I give up, I'll use the debugger as a last ditch effort to fix it... 80% of the time it works

  6. 1 week ago
    Anonymous

    GDB has a shell-like REPL in which you enter commands. Commands let you start/stop processes, set/unset breakpoints etc. Just read the fucking manual.

  7. 1 week ago
    Anonymous

    Set breakpoint, program pause there and you can read the variable contents at that point
    It's quite comfy

  8. 1 week ago
    Anonymous

    Same-ish
    I know how to set gdb to break on abort but it never let me break on line number
    I can do backtraces and print variables at least

Your email address will not be published.