11–20 of 39 posts
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...
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...
But if you have complex bugs to track, the integration of Python in GDB alone is worth the hassle, I think.
How do I use this on OS X 10.11?
You can build the gdb executable manually on OS X 10.11. First, run this if you haven't already installed the Command Line Tools for Xcode: xcode-select --install Then run these commands: curl -o gdb-7.11.tar.xz https://ftp.gnu.org/gnu/gdb/gdb-7.11.tar.xz tar zxf gdb-7.11.tar.xz cd gdb-7.11 ./configure make make install This should place the executable at /usr/local/bin/gdb. The final step is to codesign it. Instruct…
How do I use this on OS X 10.11?
You can build the gdb executable manually on OS X 10.11. First, run this if you haven't already installed the Command Line Tools for Xcode: xcode-select --install Then run these commands: curl -o gdb-7.11.tar.xz https://ftp.gnu.org/gnu/gdb/gdb-7.11.tar.xz tar zxf gdb-7.11.tar.xz cd gdb-7.11 ./configure make make install This should place the executable at /usr/local/bin/gdb. The final step is to codesign it. Instruct…
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...
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...
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:
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...
It may seem to have some mental overhead at first because you have to type commands, but it becomes second nature after a while. IMHO, it has far less overhead than debuggers where you have to click everywhere. There's a reason why people don't really bother writing pretty frontends for it.
If you use an IDE for Linux development, its debugger actually talks to GDB behind the scene. You can ditch the middle man without trouble.
The only thing that DDD really excels at (when it doesn't crash because, uh, long story short, Motif) and you can't get straight from GDB is visual representation of linked structures.
Earlier quoted context omitted.
You can build the gdb executable manually on OS X 10.11. First, run this if you haven't already installed the Command Line Tools for Xcode: xcode-select --install Then run these commands: curl -o gdb-7.11.tar.xz https://ftp.gnu.org/gnu/gdb/gdb-7.11.tar.xz tar zxf gdb-7.11.tar.xz cd gdb-7.11 ./configure make make install This should place the executable at /usr/local/bin/gdb. The final step is to codesign it. Instruct…
`tar xfJ gdb-7.11.tar.xz` for .xz files
But OS X tar is bsdtar, which ignores -z and -J when extracting because it automatically recognizes compression and does the right thing. So it turns out both our suggestions happen to work on OS X.
How do I use this on OS X 10.11?