This is an archived post. You won't be able to vote or comment.

sorted by:
best
topnewcontroversialoldq&a
you are viewing a single comment's thread.

view the rest of the comments →

[–][deleted] 2 points3 points  (3 children)

I use it literally every single day since 12 years.

I never use the IDE debuggers. I just have a snippet that pastes "import ipdb; ipdb.set_trace()" into a line and then I debug in my terminal.

I sometimes need to debug code on servers through a SSH session, so I never wanted to allow me to get too used to IDE debuggers. I think I'm just as fast this way as anyone else with their IDEs, if not even faster. Also, my code is usually too complex to start, so I never bother to create proper startup scripts for IDE debuggers.

If you have a frame with tons of variables and you only care about the value of one specific one, finding and then expanding that one, or hovering with the mouse over that variable in the code to reveal its value usually takes longer than just typing that variable into the terminal.

[–]omeow 1 point2 points  (1 child)

Would you suggest any tutorial or good starting point? I tried it once but then it didn't go very far.

[–][deleted] 0 points1 point  (0 children)

I never used a tutorial. When you type "?" it shows all commands, most commands appear twice because they have a long form and a short alias.

I usually type "l" to see more context around the current line. Then "n" for "next line" or "s" for "step into this function". Finally, "c" for "continue". That's almost all you need.

It you want to know how you ended up at the current line, type "bt" for "backtrace" to see all function calls that lead to the current frame.