I just find the way of using it, setting breakpoints and so on, to take some getting used to. Then again, I haven't tried for about 2 years so I may give it another shot. Thanks perrin.

But having said that ... where does it really score? I used to write embedded assembler, with that stuff simulators, debuggers, whatever, were almost always worth the effort. But considering that if you add some prints in your code it takes almost no time at all to rerun it, and there are other tools as well to allow you to trace ... where do you score?)

Do you use it on the command line or a graphical version? Maybe a devotee should write a debugger "quick tutorial" that takes straight to the most useful features.