What is the proper name for doing debugging by adding 'print' statements [closed]

Answer 1

Manual Assertions? Debugger Phobia?

Answer 2

I have also heard the term "MessageBox debugging" from the VB crowd to refer to this 'style' of 'debugging'.

Answer 3

(Good logging is incredibly valuable for debugging problems in running production systems. Lots of useless verbose print statements aren't, but logging something interesting when something important or unexpected occurred is incredibly important. If the only way you know how to debug problems is with a debugger, you're going to find yourself in quite the tight spot when the service you've built is broken for some of your users but you can't reproduce the problem locally.)

Answer 4

I would call it simply "logging".

Answer 5

I embedded systems its often the only method to instrument the code. Unfortunately printing takes time and effects the real-time flow of the system. So we also instrument via "tracing" where information about the state of the system (function entry exit etc) is written to a internal buffer to be dumped and parsed later. Real embedded programmers can debug by blinking an LED ;)

Answer 6

Classic Debugging