3 ms·
They use printf. Which they claim is faster.
by bluGill 2y ago
They use printf. Which they claim is faster.
- dgfitz 2y agoI'm not against printf at all, my lifetime commit history is evidence of that. Do you also think that in the case of a coredump not existing, that printf is faster? Sincere question. I'm having an internal argument with myself about it at the moment and some outside perspective would be most welcome.
- deleted 2y ago[deleted]
- bluGill 2y agoMost of my time with printf degugging is spent trying to reason about the code not compiling. though you should note that I'm repeating their claims. What I think is hidden.
- ehaliewicz2 2y agoprintf isn't faster if you want to single step through code to find math precision errors. I've had to do that on a embedded system that didn't support debugging. It was hell.
- dgfitz 2y agoI’ve always wondered why embedded devs make less than “JavaScript-FOTM” devs.
- flohofwoe 2y agoFaster than pressing F9 (to set a breakpoint on the current line) and then F5 (to start into the debugger)? Printf-debugging has its uses, but they are very niche (for instance when you don't have access to a properly integrated debugger). Logging on the other hand is useful, but logs are only one small piece of the puzzle in the overall debugging workflow - usually only for debugging problems that slipped into production and when your code runs on a server (as opposed to a user machine).
- hibbelig 2y agoIt’s very interesting. I’ve tried to observe myself. It seems that if I can see a breakpoint somewhere and then examine state and then see what the problem is, a debugger is great. If, however, it’s something where I need to examine state at multiple times in the execution, I lose track in my mind of the state I’ve seen before. This is where print debugging shines: I can see how state evolved over time and spot trends.