Testing and Debugging

Program Traces (Problems with Trace Messages)

Program traces can be time-consuming to find out which trace message to insert.
If you insert too many messages, you produce a flurry of output that is hard to analyze.
If you insert to few, you many not have enough information to spot the cause of the error.
When you are done with the program, you need to remove all the trace messages.
When you find a new error, you need to stick the print statement back in.
Many profession programmers use a debugger, not trace messages, to locate errors in their code.