Re:Three of the Hundred Falsehoods CS Students Believe
by astatine on Sunday November 10, 2019 @11:25PM
(#21502142)
> > Sprinkling printf is an efficient way to debug.
> I mostly work on threaded code, and print statements are my go to for tracking down weird timing issues.
I have found printf to subtly alter timing in threaded programs. Either masking issues or introducing them.
Anecdotally, I remember some programs being reported as working only with a printf present and bombing when removed.
Re:Three of the Hundred Falsehoods CS Students Believe
by lostcolony on Sunday November 10, 2019 @11:46PM
(#21502218)
Yeah, but the likelihood of a printf throwing the timing off is generally lower than a breakpoint.
> Sprinkling printf is an efficient way to debug.
I mostly work on threaded code, and print statements are my go to for tracking down weird timing issues. Things behave much more differently when attaching a debugger, and adding good logs makes a ton of sense long term anyway, so yeah, print statements are absolutely a great approach to debugging.
A lot of them are true, but several aren't. I guess that's the thing about lists...