You must log in or # to comment.
The entire article: You can do things with a debugger that you can’t do with print statements.
And print statements can do things that are impossible for the debugger (quick example before you start rage: last program I wrote needed some information about short-lived processes that I know only pid about. If I would use a debugger, the OS would already delete all the data I need to analyze)
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.
Wrapping the kernel with GDB is the last thing I want to do with my life :)
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.