Lines Matching refs:debugger
7 :synopsis: The Python debugger for interactive interpreters.
15 The module :mod:`pdb` defines an interactive source code debugger for Python
26 The debugger is extensible -- it is actually defined as the class :class:`Pdb`.
30 The debugger's prompt is ``(Pdb)``. Typical usage to run a program under control
31 of the debugger is::
58 useful than quitting the debugger upon program's exit.
62 in a :file:`.pdbrc` file, see :ref:`debugger-commands`.
66 ``python3 -m`` does. As with a script, the debugger will pause execution just
70 The typical usage to break into the debugger from a running program is to
75 at the location you want to break into the debugger. You can then step through
76 the code following this statement, and continue running without the debugger
101 The module defines the following functions; each enters the debugger in a
106 Execute the *statement* (given as a string or a code object) under debugger
107 control. The debugger prompt appears before any code is executed; you can
118 Evaluate the *expression* (given as a string or a code object) under debugger
127 function call returned. The debugger prompt appears as soon as the function
133 Enter the debugger at the calling stack frame. This is useful to hard-code
163 :class:`Pdb` is the debugger class.
169 patterns. The debugger will not step into frames that originate in a module
174 This allows you to break into the debugger again by pressing :kbd:`Ctrl-C`. If you
207 The commands recognized by the debugger are listed below. Most commands can be
219 Commands that the debugger doesn't recognize are assumed to be Python statements
224 statement, the exception name is printed but the debugger's state is not
227 The debugger supports :ref:`aliases <debugger-aliases>`. Aliases can have
239 triple: debugger; configuration; file
242 directory, it is read in and executed as if it had been typed at the debugger
438 ``print()`` can also be used, but is not a debugger command --- this executes the
513 resembles a debugger command. To set a global variable, you can prefix the
525 History, breakpoints, actions and debugger options are preserved.
530 Quit from the debugger. The program being executed is aborted.