Programmer Humor

32042 readers

1419 users here now

Post funny things about programming here! (Or just rant about your favourite programming language.)

Rules:

Posts must be relevant to programming, programmers, or computer science.
No NSFW content.
Jokes must be in good taste. No hate speech, bigotry, etc.

founded 5 years ago

MODERATORS

AgreeableLandscape@lemmy.ml

cat_programmer@lemmy.ml

374

Let the debugger do its job. (suppo.fi)

submitted 11 months ago by Albin7326@suppo.fi to c/programmerhumor@lemmy.ml

73 comments fedilink hide all child comments

you are viewing a single comment's thread
view the rest of the comments

[–] Scrath@feddit.de 50 points 11 months ago (2 children)

Try debugging a distributed embedded real time system which crashes when you are in a breakpoint too long because the heartbeat doesn't respond

[–] Croquette@sh.itjust.works 8 points 11 months ago (1 children)

Working with Nordic Semi Bluetooth Stack was like that when working with it a few years ago. If you reach a breakpoint while the Bluetooth stack was running, it would crash the program.

So printf to dump data while it ran and only break when absolutely necessary.

[–] uvok@pawb.social 2 points 11 months ago (1 children)

Oh? Another embedded programmer? This behavior pains me as well.

[–] Croquette@sh.itjust.works 1 points 11 months ago

Yeah. I mostly code in C because the tools come natively in C. I also do python and C# to create tools for my embedded projects.

[–] stardreamer@lemmy.blahaj.zone 6 points 11 months ago

Or just any dpdk program, where any gdb caused slowdown causes the code to "behave as expected"