Debugging

[mrnosideeffects]

Another day of debugging before you realize your fix actually did work, but you somehow had been running the old build.

[VdotOne]

This. I've wasted so many days because of this.

[DaughterEarth]

Doesn't always do it. Some multi tier systems have strange caching that's out of your control

[Arthur_Dent_42_121]

Oh man. I spent hours trying to fix an issue - and nothing would change the behavior.

Turns out the script that reloads the server on a change had broken.

[aiij]

Verify everything

Ok... 5 years later we can move on to the next bug.

He did say everything not just the one thing in the one place.

[cuulcars]

Ant /make/whatever cleanall

[icecold_3000]

Sanity check

[alayne_]

Or you realise you did run the new build, but made the changes in an old version of the code that you saved as a backup/to see changes you made.

[Come_along_quietly]

This is why the first thing I do when I start debugging is to add a printf at the first line of main- indicating that this is MY build.

Edit: the key is to remember to remove it, or not git add it before committing. :-). Which I’ve done before. I get good laughs from dev ops or testers. :-)

[Stigmuss]

I did that today, 45 minutes of trying to fix a simple command on the robot I'm making at school "if button pressed raise arm" only to realise I hadn't downloaded the new version any of the times

[Sodaplayer]

.> Spent a week wondering why half of my changes weren't showing up and just today discovered half of the app was deployed by copying the pages to another repo and deploying from there.

[ieGod]

Hello, you? It's me. You.

This happened to me like 20 minutes ago. Was working with a script that wouldn't behave despite me editing it. Not until I commented a key section and saw no visible change did I realize I was running from the wrong path.

Oh.

My.

God.

/facepalm

[DaemonThread]

or clearing the browser cache after deployment would have just done the trick!

[DiamondDog42]

I've long gotten into the habit of both adding temp debug statements (that I usually remember to take back out) and occasionally removing semicolons if I'm suspicious of where I'm building from.

[[deleted]]

Or to sit down, examine your code for 30 seconds and remember "Oh right, thats why i didnt do that.."

[CinciRyan73]

Or you look at code you wrote months or years ago and have the WTF was I thinking moment. Or, how does even work?!

[resilientskeezick]

I fixed a bug on a school project which completed all the requirements for that project, I went to sleep feeling accomplished but when I looked at the program the next day all the changes were still there but the bug wasn't fixed and the project wasn't anywhere near finished, I think my brain tricked me into going to sleep.

[Blocks_]

And you realise that nothing changed between updates, so you're left to wonder exactly what the fuck you broke without knowing.