When I work with C#, I use a debugger all the time. Learning how to attach a debugger to a running process saves a lot of headaches in the long run.
On the other hand, when I work with Python, I rarely had to use a debugger. Python's grammar is so simple that simply reading through the code is usually enough to spot most errors.
Having been spoilt by the calibre of Microsoft debugging tools earlier on in my development career it's one of the very first things I get working when approaching new environments/languages. It's especially helpful when learning a language as experimentation is often a lot quicker than RTFM.
IF the problem lends itself to debugging then a hearty "YES!" is my answer. Eclipse/Java is my debugger of choice but there are also fine standalone debuggers like JSwat or even the command line debugger.
For me, TDD, a REPL and the occasional console print statement almost completely eliminates the need for a debugger. That being said, I probably fire it up every couple of months when working on a java or .net project. #java #scala #ruby #javascript #.net
Especially when debugging JavaScript in an environment without any built-in browser debugger. If you ever have to debug JavaScript running inside a .NET WebBrowser control the debugger statement will help you keep your sanity.
[+] [-] yen223|13 years ago|reply
On the other hand, when I work with Python, I rarely had to use a debugger. Python's grammar is so simple that simply reading through the code is usually enough to spot most errors.
[+] [-] zamalek|13 years ago|reply
[+] [-] shortlived|13 years ago|reply
[+] [-] gurvinder|13 years ago|reply
[+] [-] ZephyrP|13 years ago|reply
https://github.com/zv/zdb
For "serious" stuff, I have a .gdbinit file that makes GDB much more usuable, check it out if you have time.
https://raw.github.com/zv/dotfilez/master/gdbinit
[+] [-] jk|13 years ago|reply
edit: gdb to debug asm and C code
[+] [-] gesman|13 years ago|reply
[+] [-] room271|13 years ago|reply
[+] [-] patforna|13 years ago|reply
[+] [-] codewright|13 years ago|reply
[+] [-] lifeisstillgood|13 years ago|reply
[+] [-] smilliken|13 years ago|reply
This is the nicest python debugger I've used.
[+] [-] gobengo|13 years ago|reply
[+] [-] ianox|13 years ago|reply
[+] [-] codewright|13 years ago|reply
[+] [-] mayankj08|13 years ago|reply
[+] [-] raindrift|13 years ago|reply
[+] [-] webdisrupt|13 years ago|reply
[+] [-] nekitamo|13 years ago|reply
[+] [-] Irishsteve|13 years ago|reply
[+] [-] kamaal|13 years ago|reply
Generally those situations are places where print statements are not allowed.
[+] [-] stray|13 years ago|reply
Common Lisp's debugger, accessed via slime is the best thing since running water.
Also a big fan of WingIDE's debugger for python.
[+] [-] incawater|13 years ago|reply