this post was submitted on 08 Oct 2025
263 points (99.6% liked)

Programmer Humor

26846 readers
1342 users here now

Welcome to Programmer Humor!

This is a place where you can post jokes, memes, humor, etc. related to programming!

For sharing awful code theres also Programming Horror.

Rules

founded 2 years ago
MODERATORS
Feyter@programming.dev
anzo@programming.dev
BurningTurtle@programming.dev
pylapp@programming.dev
263
Not again (infosec.pub)
submitted 5 days ago by Lojcs@piefed.social to c/programmer_humor@programming.dev
13 comments fedilink hide all child comments
you are viewing a single comment's thread
view the rest of the comments
[โ€“] meme_historian@lemmy.dbzer0.com 53 points 5 days ago* (last edited 5 days ago) (3 children)

It's a race condition that doesn't get triggered when you run the program through a debugger or with copious amounts of debug log output ๐Ÿ’€

[โ€“] Matty_r@programming.dev 2 points 2 days ago

When adding a debug print statement changes the locking of a thread and the problem doesn't occur..

[โ€“] bandwidthcrisis@lemmy.world 19 points 4 days ago

AKA heisenbug.

Observing it changes the outcome.

[โ€“] Lojcs@piefed.social 24 points 5 days ago* (last edited 5 days ago)

Or something about packaging. Or I used a function that has a different implementation for debug mode out of its intended purpose. Or