No, gdb is not what people really use. There is probably a correlation between using it and having a grey beard.
Here's an example of modern tools:
https://twitter.com/EskilSteenberg/status/169533726869157102...
Here's an example of modern tools:
https://twitter.com/EskilSteenberg/status/169533726869157102...
Watched the video and you pretty much have everything mentioned in it with just an lsp, compiler flags and a command that runs your program with a debugger. The only example that wasn't caught with just that was the p[3] example but that was caught by valgrind which is also something I have a command setup for.
Really the only thing I was actually jealous of was at the very end of the video and it wasn't the hot reloading stuff, that's easy if you split your programs from the platform its running on. The ONLY thing was that the vs debugger lets you explore variables with a visual interface instead of having to write commands to do it. I've used it on windows and even though its usually busted and variables do not always update they sometimes do. At the very least just viewing the hiearchy of the structure is useful so that you can easily add the value you want to the watch window which usually does work.
lldb does work on Linux.
That so far has been my frustration when not remote debugging linux vm, where it becomes a gdb front-end