> If your C++ application is even semi complex or uses Qt you are basically in printf land again. I mean sure go ahead use the debugger for stacktraces and such

> If your C++ application is even semi complex or uses Qt you are basically in printf land again. I mean sure go ahead use the debugger for stacktraces and such but anything beyond that is finicky. UDB, the time travel debugger I work on, supports C++ via GDB and there seem to be certain things that make life really awkward. One of my team has been looking into the combination of GCC's debug info and and GDB's behaviour around inline frames. There are a number of quirky things we see there, which boil down to "inline functions make the debug experience go wild". My understanding is that GCC isn't providing as helpful debug info as we'd like but GDB also isn't handling it in the best way. There are corner cases that can be very confusing from a user's PoV. Even in C, this is quite visible. In C++, where inlining matters even more, we'd expect it to be exaggerated further. I'd be really interested to know what things you find finicky (and are you even Linux / GCC / GDB, or is this a wider problem?)