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.

I use the command line. What I discover in the debugger and don't find when using print statements is the path that my code is taking. Sometimes it's not what I thought it was. The breakpoints and stuff are really quite simple. There's a quick reference card here.

hmmm. Been experimenting with it, spent a bit of time getting to know, and I like it. Thanks.

The debugger is worth it. It shouldn't be the first tool you reach for, but it shouldn't be far from second.

Amen. For me the biggest problem usage of the debugger is when people use it as the weapon of first resort, without taking the time to reflect on why they need to jump to the debugger.

The only think I'd add is that if you are continually reaching for the debugger then it might be time to reflect on whether there are ways you could introduce a few less bugs (e.g. spend more time refactoring your code for comprehension/maintainability, writing tests first, etc.)