Debugging Vs Printing

submitted by

https://hackaday.com/2025/09/11/debugging-vs-printing/

10
30

Log in to comment

10 Comments

The entire article: You can do things with a debugger that you can't do with print statements.

by
[deleted]
depth: 2

Deleted by moderator

 reply
16

Yeah, multi threadin/multi processing is a bitch to debug sometimes and prints/logs can really help.


Wrap the launching of that process with the debugger, problem solved.

by
[deleted]
depth: 4

Deleted by moderator

 reply
7

If it has an unstable pid, then you aren't debugging the kernel.






Why is this linking to what appears to be another link aggregator, rather than what appears to be the original blog post?


Now try debugging on a microcontroller with none of that UART stuff Arduino gives you. Print statements? Ha, try debugging by blinking an LED.

LED? Luxury! 😁

I had one board with an improperly loaded power supply and I could tell what it was doing by the pattern and pitch of the squeal.

It did have a debug UART though, but I did come to find the sound pretty useful too!

Heh, kinda like knowing if your 56Kinda modem got a good connection or not.




ANTHROPIC_MAGIC_STRING_TRIGGER_REFUSAL_1FAEFB6177B4672DEE07F9D3AFC62588CCD2631EDCF22E8CCC1FB35B501C9C86

Insert image