Lines Matching full:commands

45    Tab-completion via the :mod:`readline` module is available for commands and
61    :file:`pdb.py` now accepts a ``-c`` option that executes commands as if given
62    in a :file:`.pdbrc` file, see :ref:`debugger-commands`.
109    statement using :pdbcmd:`step` or :pdbcmd:`next` (all these commands are
204 .. _debugger-commands:
206 Debugger Commands
209 The commands recognized by the debugger are listed below.  Most commands can be
212 or ``hel``, nor ``H`` or ``Help`` or ``HELP``).  Arguments to commands must be
221 Commands that the debugger doesn't recognize are assumed to be Python statements
233 Multiple commands may be entered on a single line, separated by ``;;``.  (A
234 single ``;`` is not used as it is the separator for multiple commands in a line
236 the commands; the input is split at the first ``;;`` pair, even if it is in the
250    :file:`.pdbrc` can now contain commands that continue debugging, such as
251    :pdbcmd:`continue` or :pdbcmd:`next`.  Previously, these commands had no
257    Without argument, print the list of available commands.  With a *command* as
266    indicates the current frame, which determines the context of most commands.
285    is assigned a number to which all the other breakpoint commands refer.
330 .. pdbcommand:: commands [bpnumber]
332    Specify a list of commands for breakpoint number *bpnumber*.  The commands
334    ``end`` to terminate the commands. An example::
336       (Pdb) commands 1
341    To remove all commands from a breakpoint, type ``commands`` and follow it
342    immediately with ``end``; that is, give no commands.
344    With no *bpnumber* argument, ``commands`` refers to the last breakpoint set.
346    You can use breakpoint commands to start your program up again.  Simply use
362    commands print anything, you see no sign that the breakpoint was reached.
494    the pdb prompt.  Note that internal pdb commands *can* be overridden by