Print statement style debugging can (with effort) get a lot of stuff figured out.
But :), it's often fairly slow to go through that iteration cycle with non-trivial bugs, compared to using a debugger.
With a debugger, you start from the same place in your code you'd put your print statements. But instead of modifying the code to spit out values, the debugger will pass control of the running program to you. You can then go forwards through your program, seeing how the variable values change, which branches are taken, etc.
It'll get you to the same end result as the print statements, but faster.
Also, for complicated/hairy/weird bugs, being able to follow the actual execution can be enlightening which print statements don't really do.