>After playing around with a bit of C and trying gdb, I asked myself if this is really what people use. The display constantly breaks and there's not a lot of s

>After playing around with a bit of C and trying gdb, I asked myself if this is really what people use. The display constantly breaks and there's not a lot of stuff to quickly walk through code and visualize what it's doing. >I couldn't imagine doing anything like that with GDB. Am I just too stupid to go fast and quickly get information in GDB? Is there a better alternative that I completely missed. Is non-ABAP code just more abstract to a point where debugging in general doesn't make much sense anymore? As someone doing programming on unix since 2001, hell no, that's not what I use (directly), for the reasons you say. I mean gdb in the backend is okay. And gdb actually specifies Gdb/MI, a protocol to remote-control it. You can also use gdb directly locally this way, and then it sucks less. But nowadays I just use the IntelliJ IDEA IDE. I wrote https://github.com/daym/idea-native2-debugger https://github.com/daym/idea-native2-debugger which is a native debugger plugin (that uses gdb in the back) for IntelliJ IDEA Community Edition. You can also use CLion (requires you to subscribe--but it's totally awesome and has a lot more features) and that uses lldb in the back instead of gdb. Some of my friends use emacs with gdb debug thing. Seems to work OK too. Earlier in life I used https://www.gnu.org/software/ddd/ https://www.gnu.org/software/ddd/ a lot--but nowadays I just stay in IDEA. After you got used to IDEA, using anything else is like riding a kick-scooter after you got used to a motorcycle. emacs is also good as an IDE--but for me it just doesn't work well enough--and I'm not interested in having to maintain my editor configuration like an extra software project. You can also extend gdb with python plugins that make your variable printout nicer and/or more complete. It's very good.