News for hackers. Stuff that matters.
Re:GDB 8.1 Released by zython on Wednesday January 31, 2018 @12:29PM (#16275554)
> New shortcuts for TUI Single-Key mode: 'i' for stepi, and 'o' for nexti;

TUI really is one of the best features to really get into gdb. visually stepping through the disassembly really makes debugging more appealing, I really wish they dont abandon this aspect of gdb

Re:GDB 8.1 Released by zython on Wednesday January 31, 2018 @03:25PM (#16277234)
Seems like a I cannot edit my post, but I just remembered this brilliant short talk (15min) about gdb's TUI.

https://www.youtube.com/watch?v=PorfLSr3DDI

It really did change my opinion of gdb in just 15 min.

Re:GDB 8.1 Released by erk__ on Wednesday January 31, 2018 @01:46PM (#16276375)
My favorite visual gdb interface is the one build into emacs esspecially with gbd-many-mode
Re:GDB 8.1 Released by simark1 on Wednesday January 31, 2018 @02:40PM (#16276871)
GDB developers use it extensively, so it's not going to disappear anytime soon. Of course it's far from perfect and there are better visual interfaces for GDB, but the fact that it's a keystroke away is its strong point.
Re:GDB 8.1 Released by scottlu2 on Wednesday January 31, 2018 @12:36PM (#16275643)
Try cgdb.
Re:GDB 8.1 Released by bch on Wednesday January 31, 2018 @01:01PM (#16275910)
Since I was curious enough to look it up: https://cgdb.github.io/
Re:GDB 8.1 Released by jhasse on Wednesday January 31, 2018 @05:11PM (#16278008)
Why not use a real GUI frontend like Visual Studio Code instead?
Re:GDB 8.1 Released by flukus on Wednesday January 31, 2018 @06:08PM (#16278396)
Can you use VSCode as just a debugger? IDE's typically require sacrifices like letting the IDE take over your build process.
Re:GDB 8.1 Released by chillee on Thursday February 01, 2018 @01:03PM (#16284060)
Yep! This is all of the configuration needed to use VSCode as a debugger for Ocaml:

https://i.imgur.com/kY6NuXC.jpg

Re:GDB 8.1 Released by jhasse on Wednesday January 31, 2018 @06:42PM (#16278598)
Yes :) Install the Native Debug extension and then configure the debugger in the launch.json file.