Same here.

CLI version of gdb has worked extremely reliable for me across multiple projects and architectures (x86, arm, arm64, etc).

I have yet to encounter a bug can't be debug with gdb with some test automation + gdb script with conditional breakpoints / hw breakpoints. As long as I can reproduce the issue with test automation, I can debug it with gdb.

Most complex bugs are I have to debug was multiple threads (20+) memory leak shows up after days of testing.

I don't use GUI gdb. cli + gdb script is the best and most reliable debugging environment. I don't add printf to my code anymore, a new gdb breakpoint script + with proper debug build can replace the printf anywhere and anytime.