debugging - working effectively with gdb -


Whenever possible, I usually like to learn keyboard shortcuts. Experienced encoder effectively works effectively in the sixth one. It's really amazing to see that I'm trying to debug GDB for a while, instead of GPB debugger (on GDB basis) and me It still seems difficult to navigate through the code, observe the variable, etc. Actually, I've never experienced a GDB user, so I'm thinking ... is it worth it? Is it possible to work effectively with gdb?

Note: I also tried CGDB, which is a curse expansion of GDB. It's better, but I still think that its still not effective ...

GDB is a curses interface, which The command line can be activated by option-tui This interface has a single key mode, which provides the most common operation with a single keystroke. If additional you use automatic command execution, to display the variable value, when a breakpoint arrives, it is as comfortable and quick as it is. But if you use Eclipse anyway, then I have no point in avoiding Eclipse UI for GDB.

I used GDB inside MACS for a while but did not find the time to transfer information between GDB and MACACS, so I switched to this TUI mode mentioned above. I do not know if the information transfer between GDB and Eclipse is fast, but at least startup time of complex programs can be better in GDB directly than Eclipse.

Comments

Popular posts from this blog

excel vba - How to delete Solver(SOLVER.XLAM) code -

github - Teamcity & Git - PR merge builds - anyway to get HEAD commit hash? -

ios - Replace text in UITextView run slowly -