Not Logged In

pudb 2014.1

Its goal is to provide all the niceties of modern GUI-based debuggers in a
more lightweight and keyboard-friendly package. PuDB allows you to debug code
right where you write and test it–in a terminal. If you’ve worked with the
excellent (but nowadays ancient) DOS-based Turbo Pascal or C tools, PuDB’s UI
might look familiar.

Features

Syntax-highlighted source, the stack, breakpoints and variables are all
visible at once and continuously updated. This helps you be more aware of
what’s going on in your program. Variable displays can be expanded, collapsed
and have various customization options.

Simple, keyboard-based navigation using single keystrokes makes debugging
quick and easy. PuDB understands cursor-keys and Vi shortcuts for navigation.
Other keys are inspired by the corresponding pdb commands.

Use search to find relevant source code, or use “m” to invoke the module
browser that shows loaded modules, lets you load new ones and reload existing
ones.

Breakpoints can be set just by pointing at a source line and hitting “b” and
then edited visually in the breakpoints window. Or hit “t” to run to the line
under the cursor.

Drop to a Python shell in the current environment by pressing “!”.

PuDB places special emphasis on exception handling. A post-mortem mode makes
it easy to retrace a crashing program’s last steps.

Attaching to Running Code

An alternative to using set_trace is to use:

from pudb import set_interrupt_handler; set_interrupt_handler()

at the top of your code. This will set SIGINT (i.e., Ctrl-c) to
run set_trace, so that typing Ctrl-c while your code is running
will break the code and start debugging. See the docstring of
set_interrupt_handler for more information.

Programming PuDB

At the programming language level, PuDB displays the same interface
as Python’s built-in pdb module.
Just replace pdb with pudb.
(One exception: run is called runstatement.)

License and Dependencies

PuDB is distributed under the MIT license. It relies on the following
excellent pieces of software:

Development Version

FAQ

Q: I navigated to the Variables/Stack/Breakpoints view. How do I get
back to the source view?

A: Press your left arrow key.

Q: Where are breakpoints stored?

A: All PuDB information is stored in a location specified by the XDG Base
Directory Specification.
Usually, it is ~/.config/pudb. Breakpoints are stored in a file called
saved-breakpoints. Also in this location are the shell history from the
! shell (shell-history) and the PuDB settings (pudb.cfg).

Q: I killed PuDB and now my terminal is broken. How do I fix it?

A: Type the reset command (even if you cannot see what you are typing, it
should work). If this happens on a regular basis, please report it as a bug.