We’ll admit it. We have access to great debugging tools and, yes, sometimes they are invaluable. But most of the time, we’ll just throw a few print statements in whatever program weR…
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)
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.