potatoispeople
1794
44
1
Weeks of trying to get my code editor to connect to a debugger in a docker container, only to find out that this particular debugger has a bug in the latest version that causes it to fail to connect while in a containerized environment.
SLCtechie
My favorite is when you follow the docs exactly and it doesn’t work. You look up the error and the dev acknowledged it’s a bug and to expect a patch sometime soon. However, that post is from 4 years ago with the only recent comments since being “is this going to be fixed soon?”
SimplyWalkedIntoMordorAndBroughtPizza
99 bugs in the code, seek them out, patch them out. 12983728 bugs in the code
geoffreyfourmyle
I'm currently seeing gdb fail to find crt0.o when it starts running. Yes, that's the C runtime startup object file, the one that *every* typical process links against, the code that calls main(), the one that gdb itself had to find when it itself started running... oi.
Some days it's not worth chewing through the leather straps to get out of bed.
AtsaMattaForMe
teamsloth
GDB?
Hekatombe
If you can't trust the debugger who can you trust?
alt86er
Proper testing...
TotallyNotGLaDOS
The greatest minds of a generation worked together with the express purpose of placing the dumbest bug who ever lived into my code.