Hacker News new | past | comments | ask | show | jobs | submit login

Also:

> 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...




> > 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.


Yeah, but the likelihood of a printf throwing the timing off is generally lower than a breakpoint.


Sprinkling printf is very different from "good logs". Moreover, logging is not primarily for interactive debugging, but rather for monitoring. They're complimentary practices.


I've found sprinkling print statements to be an easy and quick alternative to setting up logging.




Guidelines | FAQ | Support | API | Security | Lists | Bookmarklet | Legal | Apply to YC | Contact

Search: