hi! do you have to deal with software that runs on the native runtime? are debuggers annoying the hell out of you?
try #rr, the time traveling debugger. it doesn't completely fix gdb, you're still going to be using gdb, but it sure helps. it is great for any kind of task involving multiple processes (rr replay -p), memory corruption (just set a memory breakpoint on the corruption then reverse-continue!), transient network conditions (repro once, play back the recording), being able to hand portable execution traces to a colleague, or just not wanting to fiddle with reproducing the problem while also operating a debugger.
it exists for x86_64 Linux (may or may not work in VMs) and arm64 Linux (where it definitely doesn't work on VMs on macOS hosts). it's pretty much indispensable for all of the worst bugs I've had to deal with.
https://github.com/rr-debugger/rr/