OK, for someone who's written a lot of C++ in Visual Studio but is now developing on Linux: is it worth learning GDB? It seems like it'll always have some mental overhead compared to a visual debugger, but on the other hand I was never crazy about using an IDE...
Use DDD instead. https://www.gnu.org/software/ddd/
GDB 7.11 released
21–30 of 39 posts
Re: GDB 7.11 released
#22OK, for someone who's written a lot of C++ in Visual Studio but is now developing on Linux: is it worth learning GDB? It seems like it'll always have some mental overhead compared to a visual debugger, but on the other hand I was never crazy about using an IDE...
https://github.com/vmorgulys/sandbox/blob/master/stackcity/t...
set pagination off
catch throw
run
bt 50
quitRe: GDB 7.11 released
#23OK, for someone who's written a lot of C++ in Visual Studio but is now developing on Linux: is it worth learning GDB? It seems like it'll always have some mental overhead compared to a visual debugger, but on the other hand I was never crazy about using an IDE...
Re: GDB 7.11 released
#24OK, for someone who's written a lot of C++ in Visual Studio but is now developing on Linux: is it worth learning GDB? It seems like it'll always have some mental overhead compared to a visual debugger, but on the other hand I was never crazy about using an IDE...
In my experience, the cgdb [1] wrapper makes gdb a viable option, by providing what I think is the sorely missing piece in vanilla gdb: a window continuously showing the code context. It also uses vim-like bindings for going into "insert" mode ("i"), versus escaping out into code context navigation mode ("ESC"). I made a short 4 minute tutorial on how to use gdb/cgdb for debugging Golang, here: https://www.youtube.co…
Re: GDB 7.11 released
#25OK, for someone who's written a lot of C++ in Visual Studio but is now developing on Linux: is it worth learning GDB? It seems like it'll always have some mental overhead compared to a visual debugger, but on the other hand I was never crazy about using an IDE...
Sure, it's not the right tool for every job, but as a simple, easy to use, ubiquitous and quick debugger, you'd do yourself a favour spending the five minutes learning how to start using it.
Re: GDB 7.11 released
#26Earlier quoted context omitted.
You still work for TicketMaster or was it long ago ?
Take a look at Terry's project if you don't know it yet: http://www.templeos.org/
Re: GDB 7.11 released
#27OK, for someone who's written a lot of C++ in Visual Studio but is now developing on Linux: is it worth learning GDB? It seems like it'll always have some mental overhead compared to a visual debugger, but on the other hand I was never crazy about using an IDE...
In my experience, the cgdb [1] wrapper makes gdb a viable option, by providing what I think is the sorely missing piece in vanilla gdb: a window continuously showing the code context. It also uses vim-like bindings for going into "insert" mode ("i"), versus escaping out into code context navigation mode ("ESC"). I made a short 4 minute tutorial on how to use gdb/cgdb for debugging Golang, here: https://www.youtube.co…
Re: GDB 7.11 released
#28OK, for someone who's written a lot of C++ in Visual Studio but is now developing on Linux: is it worth learning GDB? It seems like it'll always have some mental overhead compared to a visual debugger, but on the other hand I was never crazy about using an IDE...
Have you tried to use GDB from emacs? It's like Visual Studio
However, I do use Emacs with GUD and it works okay. If you are addicted to VI-style editing (like myself), you can use viper.
You'll want to add some keybinding to your .emacs. The following are the VS6 bindings I use:
;; Add VisualStudio-style debugging keys
;; Add convenient "until" command to gdb mode (swiped off the web)
(add-hook `gdb-mode-hook
(lambda ()
(gud-def gud-until "until %f:%l" "C-u" "Execute until current line.")))
;; Add a "jump" command (supposed to have been included in gud.el)(add-hook `gdb-mode-hook
(lambda ()
(gud-def gud-jump "tbreak %f:%l\njump %f:%l" "\C-j" "Relocate next instruction to line at point in source buffer.")))
(global-set-key [f9] 'gud-break)(global-set-key [f11] 'gud-step)
(global-set-key [f10] 'gud-next)
(global-set-key [f5] 'gud-cont)
(global-set-key [\S-f11] 'gud-finish)
(global-set-key [\C-f10] 'gud-until)
(global-set-key [\C-\S-f10] 'gud-jump) ; Equivalent to VC's Set Next Statement
Re: GDB 7.11 released
#29How do I use this on OS X 10.11?
Re: GDB 7.11 released
#30OK, for someone who's written a lot of C++ in Visual Studio but is now developing on Linux: is it worth learning GDB? It seems like it'll always have some mental overhead compared to a visual debugger, but on the other hand I was never crazy about using an IDE...