Lines Matching full:commands

93    ``next`` (all these commands are explained below).  The optional *globals* and
165 .. _debugger-commands:
167 Debugger Commands
170 The debugger recognizes the following commands.  Most commands can be
173 ``H`` or ``Help`` or ``HELP``).  Arguments to commands must be separated by
181 Commands that the debugger doesn't recognize are assumed to be Python statements
189 Multiple commands may be entered on a single line, separated by ``;;``.  (A
190 single ``;`` is not used as it is the separator for multiple commands in a line
192 the commands; the input is split at the first ``;;`` pair, even if it is in the
209    Without argument, print the list of available commands.  With a *command* as
218    indicates the current frame, which determines the context of most commands.
232    number to which all the other breakpoint commands refer.
271 commands [*bpnumber*]
272    Specify a list of commands for breakpoint number *bpnumber*.  The commands
274    terminate the commands. An example::
276       (Pdb) commands 1
281    To remove all commands from a breakpoint, type commands and follow it
282    immediately with  end; that is, give no commands.
284    With no *bpnumber* argument, commands refers to the last breakpoint set.
286    You can use breakpoint commands to start your program up again. Simply use the
299    commands print anything, you see no sign that the breakpoint was reached.
363    pdb prompt.  Note that internal pdb commands *can* be overridden by aliases.