3 ms·
Having the code, the callstack, locals, your watched variables and expressions, the threads, memory, breakpoints and machine code and registers if needed availa
by kryptiskt 1y ago
Having the code, the callstack, locals, your watched variables and expressions, the threads, memory, breakpoints and machine code and registers if needed available at a glance? As well as being able to dig deeper into data structures just by clicking on them. Why wouldn't you want that? A good GUI debugger is a dashboard showing the state of your program in a manner that is impossible to replicate in a CLI or a TUI interface.
- fingerlocks 1y agoYou get all of that in the terminal debugger. That’s why dwarf files exist.
- kryptiskt 1y agoAll the information is there, but the presentation isn't. You have to keep querying it while you're debugging. Sure, there are TUI debuggers that are more like GUI debuggers. Except that they are worse at everything compared to a GUI debugger.
- fingerlocks 1y agoI don’t know what debugger you’ve used but the entire query command is `f v` in lldb for the current stack frame
- kryptiskt 1y agoYes, but in a GUI debugger the stack and everything else is available all the time and you don't have to enter commands to see what the state is. It even highlights changes as you step. It's just so plainly superior to any terminal solution.
- jcgl 1y agoI don’t disagree that a visual debugger made with a proper GUI toolkit is better than a TUI. However, nvim-dap-ui[0] does a pretty good job. [0] https://github.com/rcarriga/nvim-dap-ui https://github.com/rcarriga/nvim-dap-ui